Efficient uplink scheduling mechanisms for dual connectivity

ABSTRACT

The present disclosure mainly relates to improvements for the buffer status reporting and the logical channel prioritization procedures performed in the UE, in scenarios where the UE is in dual connectivity and the PDCP layer of the UE is shared in the uplink for MeNB and SeNB. According to the present disclosure, a ratio is introduced according to which the buffer values for the PDCP are split in the UE between the SeNB and the MeNB according to said ratio.

TECHNICAL FIELD

The present disclosure relates to methods for communication between amobile station and a base station. In particular, it relates to animproved method for managing resource allocation for a mobile station,preferably for a mobile station capable of simultaneously connecting tomore than one cell. The present disclosure is also providing the mobilestation for participating in the methods described herein.

BACKGROUND ART

Long Term Evolution (LTE)

Third-generation mobile systems (3G) based on WCDMA radio-accesstechnology are being deployed on a broad scale all around the world. Afirst step in enhancing or evolving this technology entails introducingHigh-Speed Downlink Packet Access (HSDPA) and an enhanced uplink, alsoreferred to as High Speed Uplink Packet Access (HSUPA), giving aradio-access technology that is highly competitive. In order to beprepared for further increasing user demands and to be competitiveagainst new radio access technologies 3GPP introduced a new mobilecommunication system which is called Long Term Evolution (LTE). LTE isdesigned to meet the carrier needs for high speed data and mediatransport as well as high capacity voice support to the next decade. Theability to provide high bit rates is a key measure for LTE. The workitem (WI) specification on Long-Term Evolution (LTE) called Evolved UMTSTerrestrial Radio Access (UTRA) and UMTS Terrestrial Radio AccessNetwork (UTRAN) is finalized as Release 8 (Rel. 8 LTE). The LTE systemrepresents efficient packet based radio access and radio access networksthat provide full IP-based functionalities with low latency and lowcost. In LTE, scalable multiple transmission bandwidths are specifiedsuch as 1.4, 3.0, 5.0, 10.0, 15.0, and 20.0 MHz, in order to achieveflexible system deployment using a given spectrum. In the downlink,Orthogonal Frequency Division Multiplexing (OFDM) based radio access wasadopted because of its inherent immunity to multipath interference (MPI)due to a low symbol rate, the use of a cyclic prefix (CP), and itsaffinity to different transmission bandwidth arrangements.Single-carrier frequency division multiple access (SC-FDMA) based radioaccess was adopted in the uplink, since provisioning of wide areacoverage was prioritized over improvement in the peak data rateconsidering the restricted transmission power of the user equipment(UE). Many key packet radio access techniques are employed includingmultiple-input multiple-output (MIMO) channel transmission techniques,and a highly efficient control signaling structure is achieved in Rel. 8LTE.

LTE Architecture

The overall architecture is shown in FIG. 1 and a more detailedrepresentation of the E-UTRAN architecture is given in FIG. 2. TheE-UTRAN consists of eNBs, providing the E-UTRA user plane(PDCP/RLC/MAC/PHY) and control plane (RRC) protocol terminations towardsthe UE. The eNB hosts the Physical (PHY), Medium Access Control (MAC),Radio Link Control (RLC), and Packet data Control Protocol (PDCP) layersthat include the functionality of user-plane header-compression andencryption. It also offers Radio Resource Control (RRC) functionalitycorresponding to the control plane. It performs many functions includingradio resource management, admission control, scheduling, enforcement ofnegotiated UL QoS, cell information broadcast, ciphering/deciphering ofuser and control plane data, and compression/decompression of DL/UL userplane packet headers. The eNBs are interconnected with each other bymeans of the X2 interface. The eNBs are also connected by means of theS1 interface to the EPC (Evolved Packet Core), more specifically to theMME (Mobility Management Entity) by means of the S1-MME and to theServing Gateway (S-GW) by means of the S1-U. The S1 interface supports amany-to-many relation between MMEs/Serving Gateways and eNBs. The SGWroutes and forwards user data packets, while also acting as the mobilityanchor for the user plane during inter-eNB handovers and as the anchorfor mobility between LTE and other 3GPP technologies (terminating S4interface and relaying the traffic between 2G/3G systems and PDN GW).For idle state UEs, the SGW terminates the DL data path and triggerspaging when DL data arrives for the UE. It manages and stores UEcontexts, e.g. parameters of the IP bearer service, network internalrouting information. It also performs replication of the user traffic incase of lawful interception.

The MME is the key control-node for the LTE access-network. It isresponsible for idle mode UE tracking and paging procedure includingretransmissions. It is involved in the bearer activation/deactivationprocess and is also responsible for choosing the SGW for a UE at theinitial attach and at time of intra-LTE handover involving Core Network(CN) node relocation. It is responsible for authenticating the user (byinteracting with the HSS). The Non-Access Stratum (NAS) signalingterminates at the MME and it is also responsible for generation andallocation of temporary identities to UEs. It checks the authorizationof the UE to camp on the service provider's Public Land Mobile Network(PLMN) and enforces UE roaming restrictions. The MME is the terminationpoint in the network for ciphering/integrity protection for NASsignaling and handles the security key management. Lawful interceptionof signaling is also supported by the MME. The MME also provides thecontrol plane function for mobility between LTE and 2G/3G accessnetworks with the S3 interface terminating at the MME from the SGSN. TheMME also terminates the S6a interface towards the home HSS for roamingUEs

Component Carrier Structure in LTE

The downlink component carrier of a 3GPP LTE system is subdivided in thetime-frequency domain in so-called subframes. In 3GPP LTE each subframeis divided into two downlink slots as shown in FIG. 3, wherein the firstdownlink slot comprises the control channel region (PDCCH region) withinthe first OFDM symbols. Each subframe consists of a give number of OFDMsymbols in the time domain (12 or 14 OFDM symbols in 3GPP LTE (Release8)), wherein each OFDM symbol spans over the entire bandwidth of thecomponent carrier. The OFDM symbols thus each consists of a number ofmodulation symbols transmitted on respective N^(DL) _(RB)*N^(RB) _(sc)subcarriers as also shown in FIG. 4.

Assuming a multi-carrier communication system, e.g. employing OFDM, asfor example used in 3GPP Long Term Evolution (LTE), the smallest unit ofresources that can be assigned by the scheduler is one “resource block”.A physical resource block (PRB) is defined as N^(DL) _(symb) consecutiveOFDM symbols in the time domain (e.g. 7 OFDM symbols) and N^(RB) _(sc)consecutive subcarriers in the frequency domain as exemplified in FIG. 4(e.g. 12 subcarriers for a component carrier). In 3GPP LTE (Release 8),a physical resource block thus consists of N^(DL) _(symb)*N^(RB) _(sc)resource elements, corresponding to one slot in the time domain and 180kHz in the frequency domain (for further details on the downlinkresource grid, see for example 3GPP TS 36.211, “Evolved UniversalTerrestrial Radio Access (E-UTRA); Physical Channels and Modulation(Release 8)”, section 6.2, available at http://www.3gpp.org andincorporated herein by reference).

One subframe consists of two slots, so that there are 14 OFDM symbols ina subframe when a so-called “normal” CP (cyclic prefix) is used, and 12OFDM symbols in a subframe when a so-called “extended” CP is used. Forsake of terminology, in the following the time-frequency resourcesequivalent to the same N^(RB) _(sc) consecutive subcarriers spanning afull subframe is called a “resource block pair”, or equivalent “RB pair”or “PRB pair”.

The term “component carrier” refers to a combination of several resourceblocks in the frequency domain. In future releases of LTE, the term“component carrier” is no longer used; instead, the terminology ischanged to “cell”, which refers to a combination of downlink andoptionally uplink resources. The linking between the carrier frequencyof the downlink resources and the carrier frequency of the uplinkresources is indicated in the system information transmitted on thedownlink resources. Similar assumptions for the component carrierstructure apply to later releases too.

General Overview of the OSI Layer

FIG. 4 provides a brief overview of the OSI model on which the furtherdiscussion of the LTE architecture is based.

The Open Systems Interconnection Reference Model (OSI Model or OSIReference Model) is a layered abstract description for communication andcomputer network protocol design. The OSI model divides the functions ofa system into a series of layers. Each layer has the property that itonly uses the functions of the layer below, and only exportsfunctionality to the layer above. A system that implements protocolbehavior consisting of a series of these layers is known as a ‘protocolstack’ or ‘stack’. Its main feature is in the junction between layerswhich dictates the specifications on how one layer interacts withanother. This means that a layer written by one manufacturer can operatewith a layer from another. For the purposes of the present disclosure,only the first three layers will be described in more detail below.

The physical layer or layer 1's main purpose is the transfer ofinformation (bits) over a specific physical medium (e.g. coaxial cables,twisted pairs, optical fibers, air interface, etc.). It converts ormodulates data into signals (or symbols) that are transmitted over acommunication channel.

The purpose of the data link layer (or Layer 2) is to shape theinformation flow in a way compatible with the specific physical layer bybreaking up the input data into data frames (Segmentation AndRe-assembly (SAR) functions). Furthermore, it may detect and correctpotential transmission errors by requesting a retransmission of a lostframe. It typically provides an addressing mechanism and may offer flowcontrol algorithms in order to align the data rate with the receivercapacity. If a shared medium is concurrently used by multipletransmitters and receivers, the data link layer typically offersmechanisms to regulate and control access to the physical medium.

As there are numerous functions offered by the data link layer, the datalink layer is often subdivided into sublayers (e.g. RLC and MACsublayers in UMTS). Typical examples of Layer 2 protocols are PPP/HDLC,ATM, frame relay for fixed line networks and RLC, LLC or MAC forwireless systems. More detailed information on the sublayers PDCP, RLCand MAC of layer 2 is given later.

The network layer or Layer 3 provides the functional and proceduralmeans for transferring variable length packets from a source to adestination via one or more networks while maintaining the quality ofservice requested by the transport layer. Typically, the network layer'smain purposes are inter alia to perform network routing, networkfragmentation and congestion control functions. The main examples ofnetwork layer protocols are the IP Internet Protocol or X.25.

With respect to Layers 4 to 7 it should be noted that depending on theapplication and service it is sometimes difficult to attribute anapplication or service to a specific layer of the OSI model sinceapplications and services operating above Layer 3 often implement avariety of functions that are to be attributed to different layers ofthe OSI model. Therefore, especially in TCP(UDP)/IP based networks,Layer 4 and above is sometimes combined and forms a so-called“application layer”.

Layer Services and Data Exchange

In the following the terms service data unit (SDU) and protocol dataunit (PDU) as used herein are defined in connection with FIG. 5. Inorder to formally describe in a generic way the exchange of packetsbetween layers in the OSI model, SDU and PDU entities have beenintroduced. An SDU is a unit of information (data/information block)transmitted from a protocol at layer N+1 that requests a service from aprotocol located at layer N via a so-called service access point (SAP).A PDU is a unit of information exchanged between peer processes at thetransmitter and at the receiver of the same protocol located at the samelayer N.

A PDU is generally formed by a payload part consisting of the processedversion of the received SDU(s) preceded by a layer N specific header andoptionally terminated by a trailer. Since there is no direct physicalconnection (except for Layer 1) between these peer processes, a PDU isforwarded to the layer N−1 for processing. Therefore, a layer N PDU isfrom a layer N−1 point of view an SDU.

LTE Layer 2—User Plane and Control Plane Protocol Stack

The LTE layer 2 user-plane/control-plane protocol stack comprises threesublayers as shown in FIG. 6, PDCP, RLC and MAC. As explained before, atthe transmitting side, each layer receives a SDU from a higher layer forwhich the layer provides a service and outputs a PDU to the layer below.The RLC layer receives packets from the PDCP layer. These packets arecalled PDCP PDUs from a PDCP point of view and represent RLC SDUs froman RLC point of view. The RLC layer creates packets which are providedto the layer below, i.e. the MAC layer. The packets provided by RLC tothe MAC layer are RLC PDUs from an RLC point of view and MAC SDUs from aMAC point of view.

At the receiving side, the process is reversed, with each layer passingSDUs up to the layer above, where they are received as PDUs.

While the physical layer essentially provides a bitpipe, protected byturbo-coding and a cyclic redundancy check (CRC), the link-layerprotocols enhance the service to upper layers by increased reliability,security and integrity. In addition, the link layer is responsible forthe multi-user medium access and scheduling. One of the main challengesfor the LTE link-layer design is to provide the required reliabilitylevels and delays for Internet Protocol (IP) data flows with their widerange of different services and data rates. In particular, the protocolover-head must scale. For example, it is widely assumed that voice overIP (VoIP) flows can tolerate delays on the order of 100 ms and packetlosses of up to one percent. On the other hand, it is well-known thatTCP file downloads perform better over links with low bandwidth-delayproducts. Consequently, downloads at very high data rates (e.g., 100Mb/s) require even lower delays and, in addition, are more sensitive toIP packet losses than VoIP traffic.

Overall, this is achieved by the three sublayers of the LTE link layerthat are partly intertwined.

The Packet data Convergence Protocol (PDCP) sublayer is responsiblemainly for IP header compression and ciphering. In addition, it supportslossless mobility in case of inter-eNB handovers and provides integrityprotection to higher layer-control protocols.

The radio link control (RLC) sublayer comprises mainly ARQ functionalityand supports data segmentation and concatenation. The latter twominimize the protocol overhead independent of the data rate.

Finally, the medium access control (MAC) sublayer provides HARQ and isresponsible for the functionality that is required for medium access,such as scheduling operation and random access. FIG. 7 exemplary depictsthe data flow of an IP packet through the link-layer protocols down tothe physical layer. The Figure shows that each protocol sublayer addsits own protocol header to the data units.

Packet Data Convergence Protocol (PDCP)

The PDCP layer processes Radio Resource Control (RRC) messages in thecontrol plane and IP packets in the user plane. Depending on the radiobearer characteristics and the mode of the associated RLC entity (AM,UM, TM), the main functions performed by a PDCP entity of the PDCP layerare:

-   -   header compression and decompression (e.g. using Robust Header        Compression (ROHC) for user plane data (DRB)    -   Security functions:    -   Ciphering and deciphering for user plane and control plane data        (for SRB and DRB)    -   Integrity protection and verification for control plane data        (for SRB)    -   Maintenance of PDCP sequence numbers for SRB and DRB    -   Handover support functions:    -   In-sequence delivery and reordering of PDUs for the layer above        at handover for AM DRB;    -   Lossless handover for user plane data mapped on RLC Acknowledged        Mode (AM); including Status Reporting for AM DRBs and duplicate        elimination of lower layers SDUs for AM DRB    -   Discard for user plane data due to timeout (for SRB and DRB).

The PDCP layer manages data streams in the user plane, as well as in thecontrol plane, only for the radio bearers using either a DedicatedControl Channel (DCCH) or a Dedicated Transport Channel (DTCH). Thearchitecture of the PDCP layer differs for user plane data and controlplane data. Two different types of PDCP PDUs are defined in LTE: PDCPdata PDUs and PDCP Control PDUs. PDCP data PDUs are used for bothcontrol and user plane data. PDCP Control PDUs are only used totransport the feedback information for header compression, and for PDCPstatus reports which are used in case of handover and hence are onlyused within the user plane.

Buffer Status Reporting

The Buffer Status reporting procedure is used to provide the serving eNBwith information about the amount of data available for transmission inthe UL buffers of the UE. RRC controls BSR reporting by configuring thetwo timers periodicBSR-Timer and retxBSR-Timer and by, for each logicalchannel, optionally signalling logicalChannelGroup which allocates thelogical channel to an LCG.

For the Buffer Status reporting procedure, the UE shall consider allradio bearers which are not suspended and may consider radio bearerswhich are suspended.

A Buffer Status Report (BSR) shall be triggered if any of the followingevents occur:

-   -   UL data, for a logical channel which belongs to a LCG, becomes        available for transmission in the RLC entity or in the PDCP        entity (the definition of what data shall be considered as        available for transmission is specified in section 5.4 of        document TS36.321-a.4.0), and either the data belongs to a        logical channel with higher priority than the priorities of the        logical channels which belong to any LCG and for which data is        already available for transmission, or there is no data        available for transmission for any of the logical channels which        belong to a LCG, in which case the BSR is referred below to as        “Regular BSR”;    -   UL resources are allocated and the number of padding bits is        equal to or larger than the size of the Buffer Status Report MAC        control element plus its subheader, in which case the BSR is        referred below to as “Padding BSR”;    -   retxBSR-Timer expires and the UE has data available for        transmission for any of the logical channels which belong to a        LCG, in which case the BSR is referred below to as “Regular        BSR”;    -   periodicBSR-Timer expires, in which case the BSR is referred        below to as “Periodic BSR”.

For Regular and Periodic BSR:

-   -   if more than one LCG has data available for transmission in the        TTI where the BSR is transmitted: report Long BSR;    -   else report Short BSR.

For Padding BSR:

-   -   if the number of padding bits is equal to or larger than the        size of the Short BSR plus its subheader but smaller than the        size of the Long BSR plus its subheader:    -   if more than one LCG has data available for transmission in the        TTI where the BSR is transmitted: report Truncated BSR of the        LCG with the highest priority logical channel with data        available for transmission;    -   else report Short BSR.    -   else if the number of padding bits is equal to or larger than        the size of the Long BSR plus its subheader: report Long BSR.

If the buffer Status reporting procedure determines that at least oneBSR has been triggered and not cancelled:

-   -   if the UE has UL resources allocated for new transmission for        this TTI:    -   instruct the Multiplexing and Assembly procedure to generate the        BSR MAC control element(s);    -   start or restart periodicBSR-Timer except when all the generated        BSRs are Truncated BSRs;    -   start or restart retxBSR-Timer.    -   else if a Regular BSR has been triggered:    -   if an uplink grant is not configured or the Regular BSR was not        triggered due to data becoming available for transmission for a        logical channel for which logical channel SR masking        (logicalChannelSR-Mask) is setup by upper layers:    -   a Scheduling Request shall be triggered.

A MAC PDU shall contain at most one MAC BSR control element, even whenmultiple events trigger a BSR by the time a BSR can be transmitted inwhich case the Regular BSR and the Periodic BSR shall have precedenceover the padding BSR.

The UE shall restart retxBSR-Timer upon indication of a grant fortransmission of new data on any UL-SCH.

All triggered BSRs shall be cancelled in case the UL grant(s) in thissubframe can accommodate all pending data available for transmission butis not sufficient to additionally accommodate the BSR MAC controlelement plus its subheader. All triggered BSRs shall be cancelled when aBSR is included in a MAC PDU for transmission.

The UE shall transmit at most one Regular/Periodic BSR in a TTI. If theUE is requested to transmit multiple MAC PDUs in a TTI, it may include apadding BSR in any of the MAC PDUs which do not contain aRegular/Periodic BSR.

All BSRs transmitted in a TTI always reflect the buffer status after allMAC PDUs have been built for this TTI. Each LCG shall report at the mostone buffer status value per TTI and this value shall be reported in allBSRs reporting buffer status for this LCG.

NOTE: A Padding BSR is not allowed to cancel a triggeredRegular/Periodic BSR. A Padding BSR is triggered for a specific MAC PDUonly and the trigger is cancelled when this MAC PDU has been built.

Logical Channel Prioritization

The Logical Channel Prioritization (LCP) procedure is applied when a newtransmission is performed.

RRC controls the scheduling of uplink data by signalling for eachlogical channel:

-   -   priority where an increasing priority value indicates a lower        priority level,    -   prioritisedBitRate which sets the Prioritized Bit Rate (PBR),    -   bucketSizeDuration which sets the Bucket Size Duration (BSD).

The UE shall maintain a variable Bj for each logical channel j. Bj shallbe initialized to zero when the related logical channel is established,and incremented by the product PBR×TTI duration for each TTI, where PBRis Prioritized Bit Rate of logical channel j. However, the value of Bjcan never exceed the bucket size and if the value of Bj is larger thanthe bucket size of logical channel j, it shall be set to the bucketsize. The bucket size of a logical channel is equal to PBR×BSD, wherePBR and BSD are configured by upper layers.

The UE shall perform the following Logical Channel Prioritizationprocedure when a new transmission is performed:

-   -   The UE shall allocate resources to the logical channels in the        following steps:    -   Step 1: All the logical channels with Bj>0 are allocated        resources in a decreasing priority order. If the PBR of a radio        bearer is set to “infinity”, the UE shall allocate resources for        all the data that is available for transmission on the radio        bearer before meeting the PBR of the lower priority radio        bearer(s);    -   Step 2: the UE shall decrement Bj by the total size of MAC SDUs        served to logical channel j in Step 1

NOTE: The value of Bj can be negative.

-   -   Step 3: if any resources remain, all the logical channels are        served in a strict decreasing priority order (regardless of the        value of Bj) until either the data for that logical channel or        the UL grant is exhausted, whichever comes first. Logical        channels configured with equal priority should be served        equally.    -   The UE shall also follow the rules below during the scheduling        procedures above:    -   The UE should not segment an RLC SDU (or partially transmitted        SDU or retransmitted RLC PDU) if the whole SDU (or partially        transmitted SDU or retransmitted RLC PDU) fits into the        remaining resources;    -   if the UE segments an RLC SDU from the logical channel, it shall        maximize the size of the segment to fill the grant as much as        possible;    -   UE should maximise the transmission of data.

The UE shall not transmit data for a logical channel corresponding to aradio bearer that is suspended (the conditions for when a radio beareris considered suspended are defined in TS 36.331).

For the Logical Channel Prioritization procedure, the UE shall take intoaccount the following relative priority in decreasing order:

-   -   MAC control element for C-RNTI or data from UL-CCCH;    -   MAC control element for BSR, with exception of BSR included for        padding;    -   MAC control element for PHR or Extended PHR;    -   data from any Logical Channel, except data from UL-CCCH;    -   MAC control element for BSR included for padding.

When the UE is requested to transmit multiple MAC PDUs in one TTI, steps1 to 3 and the associated rules may be applied either to each grantindependently or to the sum of the capacities of the grants. Also theorder in which the grants are processed is left up to UE implementation.It is up to the UE implementation to decide in which MAC PDU a MACcontrol element is included when UE is requested to transmit multipleMAC PDUs in one TTI.

Further Advancements for LTE (LTE-A and 3GPP Rel. 12)

The frequency spectrum for IMT-Advanced was decided at the World Radiocommunication Conference 2007 (WRC-07). Although the overall frequencyspectrum for IMT-Advanced was decided, the actual available frequencybandwidth is different according to each region or country. Followingthe decision on the available frequency spectrum outline, however,standardization of a radio interface started in the 3rd GenerationPartnership Project (3GPP). At the 3GPP TSG RAN #39 meeting, the studyitem description on “Further Advancements for E-UTRA (LTE-Advanced)” wasapproved in the 3GPP. The study item covers technology components to beconsidered for the evolution of E-UTRA, e.g. to fulfill the requirementson IMT-Advanced.

Further, in Rel. 12 one major technology components which are currentlyunder consideration for LTE is described in the following.

Small Cells

Explosive demands for mobile data are driving changes in how mobileoperators will need to respond to the challenging requirements of highercapacity and improved quality of user experience (QoE). Currently,fourth generation wireless access systems using Long Term Evolution(LTE) are being deployed by many operators worldwide in order to offerfaster access with lower latency and more efficiency than 3G/3.5G.Nevertheless, the anticipated future traffic growth is so tremendousthat there is a vastly increased need for further network densificationto handle the capacity requirements, particularly in high traffic areas(hot spot areas) that generate the highest volume of traffic. Networkdensification—increasing the number of network nodes, and therebybringing them physically closer to the user terminals—is a key toimproving traffic capacity and extending the achievable user-data ratesof a wireless communication system. In addition to straightforwarddensification of a macro deployment, network densification can beachieved by the deployment of complementary low-power nodes respectivelysmall cells under the coverage of an existing macro-node layer. In sucha heterogeneous deployment, the low-power nodes provide very hightraffic capacity and very high user throughput locally, for example inindoor and outdoor hotspot positions.

Meanwhile, the macro layer ensures service availability and QoE over theentire coverage area. In other words, the layer containing the low-powernodes can also be referred to as providing local-area access, incontrast to the wide-area-covering macro layer. The installation oflow-power nodes respectively small cells as well as heterogeneousdeployments has been possible since the first release of LTE. In thisregard, a number of solutions have been specified in recent releases ofLTE (i.e., Release 10/11). More specifically, these releases introducedadditional tools to handle inter-layer interference in heterogeneousdeployments. In order to further optimize performance and providecost/energy-efficient operation, small cells require furtherenhancements and in many cases need to interact with or complementexisting macrocells. Such solutions will be investigated during thefurther evolution of LTE-Release 12 and beyond. In particular furtherenhancements related to low-power nodes and heterogeneous deploymentswill be considered under the umbrella of the new Rel-12 study item (SI)“Study on Small Cell Enhancements for E-UTRA and E-UTRAN”. Some of theseactivities will focus on achieving an even higher degree of interworkingbetween the macro and low-power layers, including different forms ofmacro assistance to the low-power layer and dual-layer connectivity.Dual connectivity implies that the device has simultaneous connectionsto both macro and low-power layers.

Deployment Scenarios within Small Cell Enhancement SI

This section describes the deployment scenarios assumed in the studyitem (SI) on small cell enhancements. In the following scenarios, thebackhaul technologies categorised as non-ideal backhaul in TR 36.932 areassumed. Fibre access which can be used to deploy Remote Radio Heads(RRHs) is not assumed in this study. HeNBs are not precluded, but notdistinguished from Pico eNBs in terms of deployment scenarios andchallenges even though the transmission power of HeNBs is lower thanthat of Pico eNBs. Following 3 scenarios, illustrated in FIG. 8, areconsidered:

Scenario #1. Scenario #1 is the deployment scenario where macro andsmall cells on the same carrier frequency (intra-frequency) areconnected via a non-ideal backhaul.

Scenario #2. Scenario #2 is the deployment scenario where macro andsmall cells on different carrier frequencies (inter-frequency) areconnected via a non-ideal backhaul. There are essentially two flavoursof scenario #2, which is here referred to as Scenario 2a and Scenario2b, the difference being that in scenario 2b an indoor small celldeployment is considered.

Scenario #3. Scenario #3 is the deployment scenario where only smallcells on one or more carrier frequencies are connected via a non-idealbackhaul.

Depending on the deployment scenario, different challenges/problemsexist which need to be further investigated. During the study item phasesuch challenges have been identified for the corresponding deploymentscenario and captured in TS36.842. More details on thosechallenges/problems can be found there.

In order to resolve the identified challenges which are described insection 5 of TS36.842, the following design goals are taken into accountfor this study in addition to the requirements specified in TR 36.932.

In terms of mobility robustness: for UEs in RRC_CONNECTED, Mobilityperformance achieved by small cell deployments should be comparable withthat of a macro only network.

In terms of increased signalling load due to frequent handover: any newsolutions should not result in excessive increase of signalling loadtowards the CN. However, additional signalling and user plane trafficload caused by small cell enhancements should also be taken intoaccount.

In terms of improving per-user throughput and system capacity: utilisingradio resources across macro and small cells in order to achieveper-user throughput and system capacity similar to ideal backhauldeployments while taking into account QoS requirements should betargeted.

Logical Channel Prioritization (LCP)

The finite radio resource should be allocated and used carefully amongthe UEs and radio bearers. In the downlink, the eNB is the focal pointthrough which all downlink data flows before being transmitted over theradio interface to each UE. Thus, the eNB can make consistent decisionsabout which downlink data should be transmitted first. However, in theuplink, each UE makes an individual decision based only on the data inits own buffers and the allocated radio resource. To ensure that each UEmakes the best and most consistent decisions in terms of using theallocated radio resource, the Logical Channel Prioritization (LCP)procedure is introduced. The LCP procedure is used for MAC PDUconstruction by deciding the amount of data from each logical channeland the type of MAC Control Element that should be included in the MACPDU. By using the LCP procedure, the UE can satisfy the QoS of eachradio bearer in the best and most predictable way.

In constructing a MAC PDU with data from multiple logical channels, thesimplest and most intuitive method is the absolute priority-basedmethod, where the MAC PDU space is allocated to logical channels indecreasing order of logical channel priority. This is, data from thehighest priority logical channel are served first in the MAC PDU,followed by data from the next highest priority logical channel,continuing until the MAC PDU space runs out. Although the absolutepriority-based method is quite simple in terms of UE implementation, itsometimes leads to starvation of data from low-priority logicalchannels. Starvation means that the data from the low-priority logicalchannels cannot be transmitted because the data from high-prioritylogical channels take up all the MAC PDU space.

In LTE, a Prioritized Bit Rate (PBR) is defined for each logicalchannel, in order to transmit data in order of importance but also toavoid starvation of data with lower priority. The PBR is the minimumdata rate guaranteed for the logical channel. Even if the logicalchannel has low priority, at least a small amount of MAC PDU space isallocated to guarantee the PBR. Thus, the starvation problem can beavoided by using the PBR.

Constructing a MAC PDU with PBR consists of two rounds. In the firstround, each logical channel is served in decreasing order of logicalchannel priority, but the amount of data from each logical channelincluded in the MAC PDU is initially limited to the amount correspondingto the configured PBR value of the logical channel. After all logicalchannels have been served up to their PBR values, if there is room leftin the MAC PDU, the second round is performed. In the second round, eachlogical channel is served again in decreasing order of priority. Themajor difference for the second round compared to the first round isthat each logical channel of lower priority can be allocated with MACPDU space only if all logical channels of higher priority have no moredata to transmit.

A MAC PDU may include not only the MAC SDUs from each configured logicalchannel but also the MAC CE. Except for a Padding BSR, the MAC CE has ahigher priority than a MAC SDU from the logical channels because itcontrols the operation of the MAC layer. Thus, when a MAC PDU iscomposed, the MAC CE, if it exists, is the first to be included and theremaining space is used for MAC SDUs from the logical channels. Then, ifadditional space is left and it is large enough to include a BSR, aPadding BSR is triggered and included in the MAC PDU.

The table below shows the priority order considered when generating aMAC PDU. Among the several types of MAC CE and the data from the logicalchannels, the C-RNTI MAC CE and data from the UL-CCCH have the highestpriority. The C-RNTI MAC CE and data from the UL-CCCH are never includedin the same MAC PDU. Unlike data from other logical channels, data fromthe UL-CCCH have higher priority than other MAC CEs. Because the UL-CCCHtransports an RRC message using SRB0, UL-CCCH data must have higherpriority than other data. Typically, data from the UL-CCCH aretransported during the RA procedure and the size of a MAC PDU from theUL-CCCH is limited. The C-RNTI MAC CE is used during the RA procedure bya UE whose existence is known by the eNB. Since the RA procedure issubject to collision, it is important to have a means by which the eNBcan identify each UE. Thus, the UE is required to include its C-RNTI asits identity as early as possible during the RA procedure.

TABLE 1 Priority Highest MAC CE for C-RNTI or data from UL-CCCH MAC CEfor BSR, with the exception of BSR included for padding MAC CE for PHRdata from any logical channel, except data from UL-CCCH Lowest MAC CEfor padding BSR

Priority of MAC CEs and Data from Logical Channels

The following illustrates an example of how LTE MAC multiplexing isperformed. In this example, the following are assumed:

-   -   there are three channels: channel 1 is of the highest priority,        channel 2 is of middle priority, and channel 3 is of the lowest        priority;    -   channel 1, channel 2, and channel 3 have been assigned PBR        values.

In the first round, each channel is served up to the data amountequivalent to the PBR according to the order of priority. In this firstround, a channel without any configured PBR value is not served. Inaddition, if the amount of data available for the channel is less thanthe configured value of the PBR, the channel is served up to the dataamount that is available in the buffer. Thus, each channel is allocatedspace in the MAC PDU up to its configured value of PBR.

In the second round, a logical channel is served only when the followingthree conditions are met:

-   -   after the logical channels of higher priority than the concerned        logical channel have been served;    -   there is space remaining in the MAC PDU;    -   there is data available in the channel's buffer.

Accordingly, if there is remaining space in the PDU, channel 1 is servedfirst. Because the remaining data in the buffer for channel 1 are largerthan the remaining space in the MAC PDU, all the remaining space in theMAC PDU is allocated to channel 1. Because there is no more space,channels 2 and 3 are not served in the second round.

The description above is the general principle and is not enforced everytime a new MAC PDU is composed. Each MAC SDU corresponds to one RLC PDUand one RLC PDU includes at least 1 byte of RLC PDU header. For each MACSDU, there exists a corresponding at least 1 byte MAC subheader. Thus,whenever a small amount of data from one logical channel is included ina MAC PDU, it will incur at least 2 bytes of header overhead. If theabove multiplexing principle was applied in every MAC PDU, the overalloverhead caused by the MAC subheader and the RLC PDU header of everylogical channel in a MAC PDU would be huge. Thus, rather than applyingthe above PBR requirements for every subframe, it is better to meet thePBR requirements for a long time period. To reduce the overhead and toprevent too much segmentation, the token-bucket model with PBR isapplied.

In the token-bucket model, each logical channel is associated with twoparameters: bucketSizeDuration and prioritizedBitRate. In this model, itis assumed that each logical channel is given a right to transmit aprioritizedBitRate amount of data in every subframe. If a certainlogical channel has not fully used the right to transmit itsprioritizedBitRate amount of data in a certain subframe, the remainingright can be used in another subframe. The right to transmit can beaccumulated up to a (prioritizedBitRate×bucketSizeDuration) amount ofdata. When some data for the logical channel are included in a MAC PDU,the right to transmit is decreased by the amount of data included in theMAC PDU. To prevent a certain logical channel from accumulating too muchright to transmit, the parameter bucketSizeDuration sets the limit up towhich a logical channel can accumulate the right to transmit. Throughthis token-bucket model, the UE can meet the PBR principle on averagefor a longer time period, not per subframe.

In the following, an example of logical channel prioritization isprovided. Here, for the given logical channel, it was assumed thatbucketSizeDuration was 4 ms (subframes) and prioritizedBitRate was 1Kb/ms. Thus, the logical channel cannot accumulate more than 4 Kb worthof right to transmit. In other words, even if data from the logicalchannel have not been transmitted for a long time, the maximum number ofbits that the logical channel can transmit is 4 Kb. In the example, thelogical channel has not transmitted any data for the 1st subframe to the5th subframe. But, because of the limited size of the token bucket, themaximum token accumulated by the logical channel at the 5th subframe is4 Kb. In the 6th subframe, 3 Kb of data from the logical channel havebeen transmitted. Because 1 Kb worth of token is accumulated at the 7thsubframe, the total accumulated token for the logical channel at the endof the 7th subframe is 2 Kb. Thus, even if the logical channel has nottransmitted any data, it can make a lot of transmissions at a later timethanks to the accumulated token, but no more than the maximum token.

Dual Connectivity

One promising solution which is currently under discussion in 3GPP RANworking groups is the so-called “dual connectivity” concept. The term“dual connectivity” is used to refer to an operation where a given UEconsumes radio resources provided by at least two different networknodes connected with non-ideal backhaul. Essentially UE is connectedwith both macro cell (macro eNB) and small cell (secondary eNB).Furthermore, each eNB involved in dual connectivity for a UE may assumedifferent roles. Those roles do not necessarily depend on the eNB'spower class and can vary among UEs.

Since the study Item is currently at a very early stage, details on thedual connectivity are not decided yet. For example the architecture hasnot been agreed on yet. Therefore many issues/details, e.g. protocolenhancements, are still open currently. FIG. 9 shows some exemplaryarchitecture for dual connectivity. It should be only understood as onepotential option. However the present disclosure is not limited to thisspecific network/protocol architecture but can be applied generally.Following assumptions on the architecture are made here:

-   -   Per bearer level decision where to serve each packet, C/U plane        split    -   As an example UE RRC signalling and high QoS data such as VoLTE        can be served by the Macro cell, while best effort data is        offloaded to the small cell.    -   No coupling between bearers, so no common PDCP or RLC required        between the Macro cell and small cell    -   Looser coordination between RAN nodes    -   SeNB has no connection to S-GW, i.e. packets are forwarded by        MeNB    -   Small Cell is transparent to CN.

Regarding the last two bullet points, it should be noted that it's alsopossible that SeNB is connected directly with the S-GW, i.e. S1-U isbetween S-GW and SeNB. Essentially there are three different optionswith respect to the bearer mapping/splitting:

-   -   option 1: S1-U also terminates in SeNB;    -   option 2: S1-U terminates in MeNB, no bearer split in RAN;    -   option 3: S1-U terminates in MeNB, bearer split in RAN.

FIG. 10 depicts those three options taking the downlink direction forthe U-plane data as an example. Option 2 is assumed throughout thedescription and also shown in the Figure.

A common problem of any wireless communication system is that resourcesare limited and it is not possible to allocate and use all the resourcesall the time since there is more than one potential seeker of theseresources.

This requirement gets complicated since the allocation and use of thelimited resources has to be done in view of what (resource) is minimallyrequired to serve the agreed Quality of Service (QoS) of a bearer ofeach UE and also in view of that different UEs might be experiencingdifferent radio channels and therefore would need different amount ofresources to fulfil even the similar need. The decision of resourceallocation is done for every Transmission Time Interval (TTI) which, forLTE, is 1 ms. Thus, every 1 ms, the network needs to decide how much DLresource it allocates towards each of the UEs for which there is somedata to be sent to it. Similarly, every 1 ms, the network needs todecide how much UL resource it allocates towards each of the UEs whichhave information to transmit.

The Downlink (DL) is however different from the Uplink (UL). In DL, theeNB has the complete view of the requirements of all the UEs and theirbearer(s). Namely, how much data is to be transmitted to each UE foreach of their bearers, what is the radio condition (and therefore whichresources are good/bad), QoS etc. In UL however, the network does notknow how much data the UE has send on each of its UL bearers. So, itcannot allocate a precise amount of resources for each of the UL bearerof this UE.

One possible solution could be to allocate “sufficient” amount ofresources to the UE such that all the UL bearers will be satisfied atleast ‘statistically’. However, since the resources are limited, thiswould very often mean wasting such resources and then some otherUEs/bearers will starve. For this reason the UE sends the Buffer StatusReport (BSR) from time to time, when certain conditions as specified inchapter 5.4.5 in 3GPP TS 36.321-a40 are met, so that the network hassome idea about UE's UL transmission requirements.

Another challenge is that the network has to ensure that a UEimplementation does not completely use the provided grant arbitrarilywhich might make the QoS fulfillment of the bearer(s) difficult. Forthis purpose certain rules are defined on how the UE shall use the grantacross its bearers. This is called Logical Channel Prioritization (LCP)since this is mainly about maintaining some priority between differentLogical Channels, which realize the radio bearer(s). Both Buffer StatusReporting and Logical Channel Prioritization are the functions of theMAC sub-layer of LTE Protocol Stack.

In LTE Rel. 8/9, for example, there was only one MAC entity per UE thatruns the LCP to allocate grant(s) across all bearer(s) i.e. inform theresulting grant to each of the RLC entity. Even when Carrier Aggregationwas introduced in LTE and as a result there were grants received frommore than one cell at a time, the single MAC entity was responsible forrunning LCP and allocated an applicable grant to each RLC entity. Thisis shown in the diagram of FIG. 11.

With the introduction of Small Cell Enhancements, in one of the possiblearchitecture option, it is possible that physical resources areallocated by more than one Cell to a corresponding MAC entity. In otherwords, there can be as many MAC entities in the UE as the number ofparticipating cell(s) in the UL. This is not a problem from LCP/BSRreporting point of view since these MAC schedulers can run their ownLCP, or report the BSR, and inform the resulting grant to each of theircorresponding RLC entities, such as illustrated in FIG. 12.

This is, for instance, the situation in architecture option 2 e.g. 2Cwhich is shown in FIG. 13. In architecture option 2C, the air-interfacetransmission of a particular bearer is completely via a particular cell;in the diagram of FIG. 13, the left bearer transmission is via MeNBphysical resources, and the right bearer transmission is via the SeNBphysical resources. The corresponding UE side picture of the ProtocolStack is shown in FIG. 14.

A problem arises in architecture option 3 e.g. 3C which is shown inFIGS. 15 and 16. In particular, in option 3C, the MACs in Cell 1 and 2do not know how much grant they should allocate for the shared (dashed)bearer since there is no defined rule so far. Therefore, as per today,if these MAC Schedulers strictly run the LCP, then they may end upover-allocating a grant (for instance, each allocating grant to theradio bearer equals to ‘prioritisedBitRate’) to the dashed bearer whichnow would receive grants twice. On the other hand, it defeats thefundamental purpose of Small Cell Enhancements since the network maywant to allocate maximum data to be transmitted via Cell 2 since this isthe cell that is used for offloading gain.

Similarly, it is not clear how the Buffer Status will be reported forthe data available for transmission corresponding to the dashed bearer.The buffer Status reporting procedure is used to provide the serving eNBwith information about the amount of data available for transmission inthe UL buffers of the UE. The amount of data available for transmissionis the sum of data available for transmission in PDCP and data availablefor transmission in RLC entity (the details of which are publiclyavailable in 3GPP documents TS 36.322 and 36.323). Further, since (asshown in FIG. 16) the PDCP is a common entity, the Individual RLCentities of the split-dashed-bearer (i.e. RLC of MeNB and RLC of SeNB)derive their SDUs from. Therefore, following the present specificationthe data available for transmission may double-count the same PDCP SDUsand PDCP PDUs not yet submitted to RLC, one for each MAC entity or cell.

Thus, a configuration in which the UE can communicate with at least twocells while avoiding at least some of the drawbacks illustrated above ispreferred.

CITATION LIST Non Patent Literature

-   NPL 1: 3GPP TS 36.211, “Evolved Universal Terrestrial Radio Access    (E-UTRA); Physical Channels and Modulation (Release 8),” version    8.9.0, December 2009-   NPL 2: 3GPP TS 36.321, “Evolved Universal Terrestrial Radio Access    (E-UTRA); Medium Access Control (MAC); Protocol specification    (Release 10),” version 10.4.0, December 2011-   NPL 3: 3GPP TS 36.331, “Evolved Universal Terrestrial Radio Access    (E-UTRA); Radio Resource Control (RRC); Protocol specification    (Release 10),” version 10.10.0, March 2013-   NPL 4: 3GPP TR 36.932, “Technical Specification Group Radio Access    Network; Scenarios and Requirements for Small Cell Enhancements for    E-UTRA and E-UTRAN (Release 12),” version 1.0.0, December 2012-   NPL 5: 3GPP TS36.842, “Evolved Universal Terrestrial Radio Access    (E-UTRA); Study on Small Cell Enhancements for E-UTRA and    E-UTRAN—Higher layer aspects (Release 12),” version 0.2.0, May 2013-   NPL 6: 3GPP TS 36.322, “Technical Specification Group Radio Access    Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio    Link Control (RLC) protocol specification (Release 10),” version    10.0.0, December 2010-   NPL 7: 3GPP TS 36.323, “Technical Specification Group Radio Access    Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Packet    Data Convergence Protocol (PDCP) specification (Release 11),”    version 11.0.0, September 2012

SUMMARY OF INVENTION

The above-mentioned drawbacks are overcome by the teaching of theindependent claims. Further additional advantages are achieved by theteaching of the dependent claims.

One non-limiting and exemplary embodiment of the present disclosureprovides a communication method for a mobile node connectable to amaster base station and to a secondary base station by using a splitbearer split across the master base station and the secondary basestation. A Packet Data Convergence Protocol, PDCP, layer located in themobile node is shared for the split bearer between the master basestation and the secondary base station. In this method the mobile nodesplits a total buffer occupancy of the PDCP layer in the mobile nodebetween the master base station and the secondary base station based ona split ratio, into a first PDCP buffer occupancy value for the masterbase station and a second PDCP buffer occupancy value for the secondarybase station. The mobile node generates a first buffer status report forthe master base station based on the first PDCP buffer occupancy value,and further also generates a second buffer status report for thesecondary base station based on the second PDCP buffer occupancy value.Subsequently, the mobile node transmits the first buffer status reportto the master base station, and transmits the second buffer statusreport to the secondary base station.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, a particular split ratio is defined such that one of thefirst and second PDCP buffer occupancy values is equal to the totalbuffer occupancy of the PDCP layer in the mobile node for the splitbearer, and such that the other one of the first and second PDCP bufferoccupancy values is equal to zero. Preferably, said particular splitratio is expressed by 1 to 0 or 0 to 1.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, when being configured with the particular split ratio, themobile node transmit all uplink data, processed by the PDCP layer, toeither the master base station or the secondary base station dependingon the particular split ratio, with the exception of RLC uplink databeing transmitted to the respective base station.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, when being configured with the particular split ratio, themobile node deactivates the split bearer for uplink data, processed bythe PDCP layer, to either the master base station or the secondary basestation depending on the particular split ratio.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, the mobile node is informed by the master base stationabout how to split the total buffer occupancy of the PDCP layer in themobile node between the master base station and the secondary basestation. Preferably this may be done by a flag in an information elementassociated with the split bearer.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, a first Radio Link Control, RLC layer is located in themobile node for the split bearer to the master base station, and asecond RLC layer is located in the mobile node for the split bearer tothe secondary base station. The first buffer status report is generatedby the mobile node based on the sum of the first PDCP buffer occupancyvalue and a buffer occupancy value of the first RLC layer in the mobilenode. The second buffer status report is generated by the mobile nodebased on the sum of the second PDCP buffer occupancy value and a bufferoccupancy value of the second RLC layer in the mobile node.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, a particular split ratio is defined such that one of thefirst and second PDCP buffer occupancy values is equal to the totalbuffer occupancy of the PDCP layer in the mobile node for the splitbearer, and such that the other one of the first and second PDCP bufferoccupancy values is equal to zero. Furthermore, in case the firstrespectively second buffer status report is zero, the first respectivelysecond buffer status report is not transmitted.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, the mobile node is configured to transmit all theacknowledgements of the Transmission Control Protocol, TCP, layer,relating to TCP downlink data received in the mobile node, to the masterbase station. This is preferably done independent from whether or notthe remaining uplink data is transmitted by the mobile node to themaster base station.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, the PDCP layer of the mobile node detects TCPacknowledgments and internally forwards the detected TCPacknowledgements to lower layers to be transmitted via a channel to themaster base station.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, the calculation of the first buffer status reportconsiders the transmission of all the acknowledgements of the TCP layerto the master base station, irrespective of the split ratio.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, the mobile node performs a first Logical ChannelPrioritization, LCP, procedure for the split bearer to the master basestation, based on the value of the buffer occupancy for the split bearerto the master base station reported with the first buffer status report.Similarly, the mobile node performs a second Logical ChannelPrioritization, LCP, procedure for the split bearer to the secondarybase station, based on the value of the buffer occupancy for the splitbearer to the secondary base station reported with the second bufferstatus report.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, the value of the buffer occupancy reported with the firstbuffer status report is considered in the first LCP procedure by servingresources to the split bearer to the master base station as a maximum upto the value of the buffer occupancy reported with the first bufferstatus report for the split bearer to the master base station. The valueof the buffer occupancy reported with the second buffer status report isconsidered in the second LCP procedure by serving resources to the splitbearer to the secondary base station as a maximum up to the value of thebuffer occupancy reported with the second buffer status report for thesplit bearer to the secondary base station.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, a first Media Access Control, MAC, layer is located in themobile node for the split bearer to the master base station, and asecond MAC layer is located in the mobile node for the split bearer tothe secondary base station. When buffer status reporting is triggered inthe first MAC layer due to data arrival in the buffer of the splitbearer, the first MAC layer triggers the buffer status reporting in thesecond MAC layer for the split bearer. When buffer status reporting istriggered in the second MAC layer due to data arrival in the buffer ofthe split bearer, the second MAC layer triggers the buffer statusreporting in the first MAC layer for the split bearer.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, the first buffer status report is generated by the firstMAC layer at the time of being triggered, and the second buffer statusreport is generated by the second MAC layer at the time of beingtriggered. Alternatively, in case the first buffer status report isscheduled to be transmitted before second buffer status report, thefirst buffer status report is generated by the first MAC layer at thetime the first buffer status report is scheduled to be transmitted tothe master base station, and the second buffer status report isgenerated by the second MAC layer at the time the first buffer statusreport is scheduled to be transmitted to the master base station. Stillalternatively to the above, the first buffer status report is generatedby the first MAC layer at the time the first buffer status report isscheduled to be transmitted to the master base station, and the secondbuffer status report is generated by the second MAC layer at the timethe second buffer status report is scheduled to be transmitted to thesecondary base station. Still further alternatively to the above, thefirst buffer status report is generated by the first MAC layer at thetime the first buffer status report is scheduled to be transmitted tothe master base station or at the time the first buffer status report istriggered at the first MAC layer, and the second buffer status report isgenerated by the second MAC layer at the time the second buffer statusreport is scheduled to be transmitted to the secondary base station,wherein the second buffer status report includes the value of the datanot reported by the first buffer status report.

According to an alternative and advantageous variant of the embodimentof the present disclosure which can be used in addition or alternativelyto the above, a first Media Access Control, MAC, layer is located in themobile node for the split bearer to the master base station, and asecond MAC layer is located in the mobile node for the split bearer tothe secondary base station. Buffer status reporting is triggered in thefirst MAC layer due to data arrival in the buffer of the split bearer.Buffer status reporting is triggered in the second MAC layer due to dataarrival in the buffer of the split bearer.

The embodiment further provides a mobile node connectable to a masterbase station and to a secondary base station by using a split bearersplit across the master base station and the secondary base station. APacket Data Convergence Protocol, PDCP, layer located in the mobile nodeis shared for the split bearer between the master base station and thesecondary base station. A processor of the mobile node splits a totalbuffer occupancy of the PDCP layer in the mobile node between the masterbase station and the secondary base station, based on a split ratio,into a first PDCP buffer occupancy value for the master base station anda second PDCP buffer occupancy value for the secondary base station. Theprocessor generates a first buffer status report for the master basestation based on the first PDCP buffer occupancy value, and generates asecond buffer status report for the secondary base station based on thesecond PDCP buffer occupancy value. A transmitter of the mobile nodetransmits the first buffer status report to the master base station, andtransmitting the second buffer status report to the secondary basestation.

An embodiment of the present disclosure provides a communication methodfor a mobile node connectable to a master base station and to asecondary base station by using a logical channel shared by the masterbase station and the secondary base station. A Packet Data ConvergenceProtocol, PDCP, layer is located in the mobile node and shared for theshared logical channel between the master base station and the secondarybase station. The mobile node splits a total buffer occupancy of thePDCP layer in the mobile node between the master base station and thesecondary base station based on a split-buffer ratio, into a first PDCPbuffer occupancy value for the master base station and a second PDCPbuffer occupancy value for the secondary base station. The mobile nodegenerates a first buffer status report for the master base station basedon the first PDCP buffer occupancy value, and generates a second bufferstatus report for the secondary base station based on the second PDCPbuffer occupancy value. The mobile node transmits the first bufferstatus report to the master base station, and transmits the secondbuffer status report to the secondary base station.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the split-buffer ratio is determined by the master base station,preferably based on at least one of: a load handled by the SecondaryBase Station, offload requirements, channel conditions, quality ofservice. The determined split-buffer ratio is transmitted from themaster base station to the mobile node and/or the secondary basestation, preferably using Radio Resource Control, RRC, signalling, orMedia Access Control, MAC, signalling.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the split-buffer ratio is determined by the mobile node, preferablybased on at least one of: radio thresholds of the radio links betweenthe mobile node and respectively the master and secondary base station,past resource grants received by the mobile node. The determinedsplit-buffer ratio is transmitted from the mobile node to the masterbase station and/or the secondary base station, preferably using RadioResource Control, RRC, signalling, or Media Access Control, MAC,signalling.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,a first Radio Link Control, RLC layer is located in the mobile node forthe shared logical channel to the master base station, and a second RLClayer is located in the mobile node for the shared logical channel tothe secondary base station. The first buffer status report is generatedby the mobile node based on the sum of the first PDCP buffer occupancyvalue and a buffer occupancy value of the first RLC layer in the mobilenode. The second buffer status report is generated by the mobile nodebased on the sum of the second PDCP buffer occupancy value and a bufferoccupancy value of the second RLC layer in the mobile node.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the mobile node is connectable to the master base station and to thesecondary base station by using a plurality of logical channels sharedbetween the master base station and the secondary base station. Thesplit-buffer ratio is applied to only one or a set of logical channelsout of the plurality of shared logical channels, or the split-bufferratio is applied to all of the plurality of shared logical channels.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,determining whether the total buffer occupancy of the PDCP layer and theRLC layer in the mobile node exceeds a pre-determined threshold or not.If yes, the steps of splitting the total buffer occupancy, generatingand transmitting the first and second buffer status reports areperformed. If no, the steps of splitting the total buffer occupancy,generating and transmitting the first and second buffer status reportsare not performed, and the mobile node generates and transmits itsuplink data buffer status report to only one of the master or secondarybase station.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the mobile node transmits the first buffer status report for the masterbase station to the secondary base station, preferably for the secondarybase station to estimate the amount of resources the mobile stationmight be allocated in the next few subframes from the master basestation. The mobile node transmits the second buffer status report forthe secondary base station to the master base station, preferably forthe master base station to estimate the amount of resources the mobilestation might be allocated in the next few subframes from the secondarybase station.

An embodiment of the present disclosure provides further a mobile nodeconnectable to a master base station and to a secondary base station byusing a logical channel shared by the master base station and thesecondary base station. A Packet Data Convergence Protocol, PDCP, layerlocated in the mobile node is shared for the shared logical channelbetween the master base station and the secondary base station. Aprocessor of the mobile node splits a total buffer occupancy of the PDCPlayer in the mobile node between the master base station and thesecondary base station, based on a split-bearer buffer ratio, into afirst PDCP buffer occupancy value for the master base station and asecond PDCP buffer occupancy value for the secondary base station. Aprocessor of the mobile node generates a first buffer status report forthe master base station based on the first PDCP buffer occupancy value,and generates a second buffer status report for the secondary basestation based on the second PDCP buffer occupancy value. A transmitterof the mobile node transmits the first buffer status report to themaster base station, and transmits the second buffer status report tothe secondary base station.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,a receiver of the mobile node receives from the master base station thesplit-buffer ratio, determined by the master base station, preferablyusing Radio Resource Control, RRC, signalling, or Media Access Control,MAC, signalling.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the split-buffer ratio is determined by the mobile node, preferablybased on at least one of: radio thresholds of the radio links betweenthe mobile node and respectively the master and secondary base station,past resource grants received by the mobile node. The transmittertransmits the determined split-buffer ratio to the master base stationand/or the secondary base station, preferably using Radio ResourceControl, RRC, signalling, or Media Access Control, MAC, signalling.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,a first Radio Link Control, RLC layer is located in the mobile node forthe shared logical channel to the master base station, and a second RLClayer is located in the mobile node for the shared logical channel tothe secondary base station. The processor generates the first bufferstatus report based on the sum of the first PDCP buffer occupancy valueand a buffer occupancy value of the first RLC layer in the mobile node.The processor generates the second buffer status report based on the sumof the second PDCP buffer occupancy value and a buffer occupancy valueof the second RLC layer in the mobile node.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the processor determines whether the total buffer occupancy of the PDCPlayer and the RLC layer in the mobile node exceeds a pre-determinedthreshold or not. If yes, the steps of splitting the total bufferoccupancy, generating and transmitting the first and second bufferstatus reports are performed. If no, the steps of splitting the totalbuffer occupancy, generating and transmitting the first and secondbuffer status reports are not performed, and the mobile node generatesand transmits its uplink data buffer status report to only one of themaster or secondary base station.

An embodiment of the present disclosure provides further a master basestation for use in a mobile communication system, where a mobile node isconnected to the master base station and to a secondary base station byusing a logical channel shared by the master base station and thesecondary base station. A Packet Data Convergence Protocol, PDCP, layerlocated in the mobile node is shared for the shared logical channelbetween the master base station and the secondary base station. Aprocessor of the master base station determines a split-buffer ratio,preferably based on at least one of: a load handled by the SecondaryBase Station, offload requirements, channel conditions, quality ofservice. The split-buffer ratio is for use by the mobile node to split atotal buffer occupancy of the PDCP layer in the mobile node between themaster base station and the secondary base station based on thesplit-buffer ratio, into a first PDCP buffer occupancy value for themaster base station and a second PDCP buffer occupancy value for thesecondary base station. A transmitter transmits the determinedsplit-buffer ratio to the mobile node and/or the secondary base station,preferably using Radio Resource Control, RRC, signalling, or MediaAccess Control, MAC, signalling.

A further embodiment of the present disclosure provides a method for amobile node connectable to a master base station and to a secondary basestation by using a logical channel shared by the master base station andthe secondary base station. A Packet Data Convergence Protocol, PDCP,layer located in the mobile node is shared for the shared logicalchannel between the master base station and the secondary base station.A first Radio Link Control, RLC layer is located in the mobile node forthe shared logical channel to the master base station, and a second RLClayer is located in the mobile node for the shared logical channel tothe secondary base station. The mobile node transmits a total bufferoccupancy value of the PDCP layer in the mobile node, a buffer occupancyvalue of the first RLC layer and a buffer occupancy value of the secondRLC layer, to the master base station and/or the secondary base station.Either the master base station or the secondary base station determine asplit ratio, based on the received total buffer occupancy value of thePDCP layer in the mobile node, the buffer occupancy value of the firstRLC layer and the buffer occupancy value of the second RLC layer. Thedetermined split ratio is transmitted to the other one of the masterbase station and the secondary base station. The master base station andsecondary base station, perform the uplink resource allocation for theshared logical channel, respectively based on the split ratio, such thatthe uplink resource allocation for the shared logical channel for thedata as indicated by the received total occupancy value of the PDCPlayer is split between the master base station and the secondary basestation according to the split ratio.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the master base station configures the shared logical channel to bealone within a logical channel group.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the mobile node determines to which base station to transmit the totalbuffer occupancy value of the PDCP layer in the mobile node, the bufferoccupancy value of the first RLC layer and the buffer occupancy value ofthe second RLC layer, preferably based on at least one of:

-   -   past resource allocations received from the secondary base        station and master base station,    -   radio link thresholds,    -   the amount of buffer occupancy,    -   whether or not previous resource allocations from the secondary        base station or master base station were enough for the mobile        node to transmit all data.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the mobile node determines to which base station to transmit the totalbuffer occupancy value of the PDCP layer in the mobile node, the bufferoccupancy value of the first RLC layer and the buffer occupancy value ofthe second RLC layer.

The further embodiment of the present disclosure provides a mobile nodeconnectable to a master base station and to a secondary base station byusing a logical channel shared by the master base station and thesecondary base station. A Packet Data Convergence Protocol, PDCP, layerlocated in the mobile node is shared for the shared logical channelbetween the master base station and the secondary base station. A firstRadio Link Control, RLC layer is located in the mobile node for theshared logical channel to the master base station, and a second RLClayer is located in the mobile node for the shared logical channel tothe secondary base station. A transmitter of the mobile node transmits atotal buffer occupancy value of the PDCP layer in the mobile node, abuffer occupancy value of the first RLC layer and a buffer occupancyvalue of the second RLC layer, to the master base station and thesecondary base station, for the master or secondary base station todetermine a split ratio, based on which the uplink resource allocationfor the shared logical channel is respectively performed by the masterand secondary base station, such that the uplink resource allocation forthe shared logical channel for the data as indicated by the receivedtotal occupancy value of the PDCP layer is split between the master basestation and the secondary base station according to the split ratio.

The further embodiment of the present disclosure provides a master basestation for use in a mobile communication system, wherein a mobile nodeis connectable to the master base station and to a secondary basestation by using a logical channel shared by the master base station andthe secondary base station. A Packet Data Convergence Protocol, PDCP,layer located in the mobile node is shared for the shared logicalchannel between the master base station and the secondary base station.A first Radio Link Control, RLC layer is located in the mobile node forthe shared logical channel to the master base station, and a second RLClayer is located in the mobile node for the shared logical channel tothe secondary base station. A receiver of the master base stationreceives from the mobile node a total buffer occupancy value of the PDCPlayer in the mobile node, a buffer occupancy value of the first RLClayer and a buffer occupancy value of the second RLC layer. A processorof the master base station determines a split ratio, based on thereceived total buffer occupancy value of the PDCP layer in the mobilenode, the buffer occupancy value of the first RLC layer and the bufferoccupancy value of the second RLC layer. A transmitter of the masterbase station transmits the determined split ratio to the secondary basestation. The processor performs the uplink resource allocation for theshared logical channel, based on the split ratio, such that the uplinkresource allocation for the shared logical channel for the data asindicated by the received total occupancy value of the PDCP layer issplit between the master base station and the secondary base stationaccording to the split ratio.

A still further embodiment of the present disclosure provides acommunication method for a mobile node connectable to a master basestation and to a secondary base station by using a logical channelshared by the master base station and the secondary base station. APacket Data Convergence Protocol, PDCP, layer located in the mobile nodeis shared for the shared logical channel between the master base stationand the secondary base station. A prioritized bitrate parameter used fora logical channel prioritization, LCP, procedure, is split into a firstprioritized bitrate parameter for the LCP, procedure for the sharedlogical channel to the master base station, and into a secondprioritized bitrate parameter for the LCP procedure for the sharedlogical to the secondary base station, The mobile node performs a firstLCP procedure for the shared logical channel to the master base station,based on the first prioritized bitrate parameter. The mobile nodeperforms a second LCP procedure for the shared logical channel to thesecondary base station, based on the second prioritized bitrateparameter.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the first LCP procedure is performed by a Media Access Control, MAC,entity in the mobile node responsible for the master base station, andthe LCP procedure is performed by a MAC entity in the mobile noderesponsible for the secondary base station.

The still further embodiment of the present disclosure provides a mobilenode connectable to a master base station and to a secondary basestation by using a logical channel shared by the master base station andthe secondary base station. A Packet Data Convergence Protocol, PDCP,layer located in the mobile node is shared for the shared logicalchannel between the master base station and the secondary base station.A processor of the mobile node splits a prioritized bitrate parameterused for a logical channel prioritization, LCP, procedure, into a firstprioritized bitrate parameter for the LCP, procedure for the sharedlogical channel to the master base station, and into a secondprioritized bitrate parameter for the LCP procedure for the sharedlogical to the secondary base station. The processor performs a firstLCP procedure for the shared logical channel to the master base station,based on the first prioritized bitrate parameter, and performs a secondLCP procedure for the shared logical channel to the secondary basestation, based on the second prioritized bitrate parameter.

Another embodiment of the present disclosure provides a communicationmethod for a mobile node connectable to a master base station and to asecondary base station by using a logical channel shared by the masterbase station and the secondary base station. A Packet Data ConvergenceProtocol, PDCP, layer located in the mobile node is shared for theshared logical channel between the master base station and the secondarybase station. The mobile node performs a first logical channelprioritization, LCP, procedure, for the shared logical channel to eitherthe master base station or to the secondary base station, based on aprioritized bitrate parameter, including updating the prioritizedbitrate parameter by the mobile node based on the first LCP procedure.After finishing the first LCP procedure by the mobile node, the mobilenode performs a second LCP procedure of the shared logical channel tothe other base station, secondary base station or master base station,based on the updated prioritized bitrate parameter.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the mobile node determines whether the first LCP procedure for theshared logical channel is either to the master base station or to thesecondary base station, according to one of the following:

-   -   the first LCP procedure is always for the shared logical channel        to the secondary base station, whereas the second LCP procedure        is always for the shared logical channel to the master base        station,    -   the first LCP procedure is always for the shared logical channel        to the master base station, whereas the second LCP procedure is        always for the shared logical channel to the secondary base        station,    -   is determined on a random basis,    -   based on previous uplink resource allocations received from the        master base station and the secondary base stations,    -   based on the amount of unsatisfied prioritized bitrate for the        LCP procedure for the shared logical channel to the master base        station, and/or based on the amount of unsatisfied prioritized        bitrate for the LCP procedure for the shared logical channel to        the secondary base station,

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the steps of performing the first and second LCP procedures areperformed by the mobile node every transmission time interval.

This another embodiment further provides a mobile node connectable to amaster base station and to a secondary base station by using a logicalchannel shared by the master base station and the secondary basestation. A Packet Data Convergence Protocol, PDCP, layer located in themobile node is shared for the shared logical channel between the masterbase station and the secondary base station. A processor of the mobilenode performs a first logical channel prioritization, LCP, procedure,for the shared logical channel to either the master base station or tothe secondary base station, based on a prioritized bitrate parameter,including updating the prioritized bitrate parameter by the mobile nodebased on the first LCP procedure. The processor performs, afterfinishing the first LCP procedure, a second LCP procedure of the sharedlogical channel to the other base station, secondary base station ormaster base station, based on the updated prioritized bitrate parameter.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the steps of performing the first and second LCP procedures areperformed by the processor of the mobile node every transmission timeinterval.

A still another embodiment of the present disclosure provides acommunication method for a mobile node connectable to a master basestation and to a secondary base station by using a logical channelshared by the master base station and the secondary base station. APacket Data Convergence Protocol, PDCP, layer located in the mobile nodeis shared for the shared logical channel between the master base stationand the secondary base station. A first Media Access Control, MAC,entity in the mobile node is responsible to perform logical channelprioritization, LCP, procedures regarding the master base station. Asecond MAC entity in the mobile node is responsible to perform LCPprocedure regarding the secondary base station. One of the first orsecond MAC entity in the mobile node performs a first LCP procedure forthe shared logical channel, during a particular first number oftransmission time intervals. After performing the first LCP procedureduring the particular first number of transmission time intervals, theother one of the first or second MAC entity in the mobile node performsa second LCP procedure for the shared logical channel, during aparticular second number of transmission time intervals.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the other one of the first or second MAC entity performs a third LCPprocedure for other logical channels than the shared logical channel,during the first number of transmission time intervals. The one of thefirst or second MAC entity performs a fourth LCP procedure for otherlogical channels than the shared logical channel, during the secondnumber of transmission time intervals.

This embodiment further provides a mobile node connectable to a masterbase station and to a secondary base station by using a logical channelshared by the master base station and the secondary base station. APacket Data Convergence Protocol, PDCP, layer located in the mobile nodeis shared for the shared logical channel between the master base stationand the secondary base station. A first Media Access Control, MAC,entity in the mobile node is responsible to perform logical channelprioritization, LCP, procedures regarding the master base station. Asecond MAC entity in the mobile node is responsible to perform LCPprocedure regarding the secondary base station. A processor of themobile node performs via the one of the first or second MAC entity inthe mobile node a first LCP procedure for the shared logical channel,during a particular first number of transmission time intervals. Theprocessor performs, after performing the first LCP procedure during theparticular first number of transmission time intervals, via the otherone of the first or second MAC entity, a second LCP procedure for theshared logical channel, during a particular second number oftransmission time intervals.

According to an advantageous variant of the embodiment of the presentdisclosure which can be used in addition or alternatively to the above,the processor performs via the other one of the first or second MACentity a third LCP procedure for other logical channels than the sharedlogical channel, during the first number of transmission time intervals.The processor performs via one of the first or second MAC entity afourth LCP procedure for other logical channels than the shared logicalchannel, during the second number of transmission time intervals.

A further embodiment of the present disclosure provides a communicationmethod for a mobile node connectable to a master base station and to asecondary base station by using a logical channel shared by the masterbase station and the secondary base station. A Packet Data ConvergenceProtocol, PDCP, layer located in the mobile node is shared for theshared logical channel between the master base station and the secondarybase station. The master base station determines a first resourceallocation for the mobile node with respect to the plurality of logicalchannels of the master base station, including the shared logicalchannel, and transmitting same to the mobile node. The secondary basestation determines a second resource allocation for the mobile node withrespect to the plurality of logical channels of the secondary basestation, including the shared logical channel, and transmitting same tothe mobile node. The mobile node determines the amount of unsatisfiedprioritized bitrate or of remaining buffer for each of the plurality oflogical channels, except for the shared logical channel, based on thefirst and second resource allocations. The mobile node reallocatesresources from either the received first or the received second resourceallocation regarding to the shared logical channel, to the logicalchannels having an unsatisfied prioritized bitrate or remaining bufferin a logical channel order where the logical channel with the highestunsatisfied prioritized bitrate is first.

The further embodiment also provides a mobile node connectable to amaster base station and to a secondary base station by using a logicalchannel shared by the master base station and the secondary basestation. A Packet Data Convergence Protocol, PDCP, layer located in themobile node is shared for the shared logical channel between the masterbase station and the secondary base station. A receiver of the mobilenode receives from the master base station a first resource allocationfor the mobile node with respect to the plurality of logical channels ofthe master base station, including the shared logical channel. Thereceiver receives from the secondary base station a second resourceallocation for the mobile node with respect to the plurality of logicalchannels of the secondary base station, including the shared logicalchannel. A processor of the mobile node determines the amount ofunsatisfied prioritized bitrate or of remaining buffer for each of theplurality of logical channels, except for the shared logical channel,based on the first and second resource allocations. The processorreallocates resources from either the received first or the receivedsecond resource allocation regarding to the shared logical channel, tothe logical channels having an unsatisfied prioritized bitrate orremaining buffer, in a logical channel order where the logical channelwith the highest unsatisfied prioritized bitrate is first.

These general and specific aspects may be implemented using a system, amethod, and a computer program, and any combination of systems, methods,and computer programs. Additional benefits and advantages of thedisclosed embodiments will be apparent from the specification andFigures. The benefits and/or advantages may be individually provided bythe various embodiments and features of the specification and Figures,and need not all be provided in order to obtain one or more of the same.

BRIEF DESCRIPTION OF DRAWINGS

The present disclosure will be better understood with reference to theaccompanying drawings. The corresponding embodiments are only possibleconfiguration in which the individual features may, however, asdescribed above, be implemented independently of each other or may beomitted. Equal elements illustrated in the drawings are provided withequal reference signs. Parts of the description relating to equalelements illustrated in the drawings may be left out.

FIG. 1 schematically shows an exemplary architecture of a 3GPP LTEsystem,

FIG. 2 schematically shows an exemplary overview of the overall E-UTRANarchitecture of 3GPP LTE,

FIG. 3 schematically shows exemplary subframe boundaries on a downlinkcomponent carrier as defined for 3GPP LTE (Release 8/9),

FIG. 4 schematically illustrates the OSI model with the different layersfor communication,

FIG. 5 schematically illustrates the relationship of a protocol dataunit (PDU) and a service data unit (SDU) as well as the inter-layerexchange of same,

FIG. 6 schematically illustrates the layer 2 user and control-planeprotocol stack composed of the three sublayers, PDCP, RLC and MAC,

FIG. 7 schematically gives an overview of the different functions in thePDCP, RLC and MAC layers as well as illustrates exemplary the processingof SDUs/PDUs by the various layers,

FIG. 8 schematically shows four possible dual cell scenarios,

FIG. 9 schematically shows exemplary architectures for dualconnectivity,

FIG. 10 schematically shows various options in the DL direction for theU-plane data;

FIG. 11 schematically shows a single MAC entity receiving grants frommore than one cell,

FIG. 12 schematically shows two MAC cells receiving grants from twocells without split-bearers,

FIG. 13 schematically shows a network side, user plane architectureoption 2C,

FIG. 14 schematically shows a UE side, user plane architecture option2C,

FIG. 15 schematically shows a network side, user plane architectureoption 3C,

FIG. 16 schematically shows a UE side, user plane architecture option3C,

FIG. 17 schematically shows In UP architecture option 3C and 3D, wherethe PDCP is a common entity,

FIG. 18 schematically shows an example of an application of a ratio forderiving the BSR,

FIG. 19 schematically shows a UE side user plane architecture option 3Caccording to one embodiment of the present disclosure,

FIG. 20 schematically shows a UE side user plane architecture option 3Caccording to one embodiment of the present disclosure.

DESCRIPTION OF EMBODIMENTS

In the present description, use is made of the following terms.

A “mobile station” or “mobile node” is a physical entity within acommunication network. One node may have several functional entities. Afunctional entity refers to a software or hardware module thatimplements and/or offers a predetermined set of functions to otherfunctional entities of a node or the network. Nodes may have one or moreinterfaces that attach the node to a communication facility or mediumover which nodes can communicate. Similarly, a network entity may have alogical interface attaching the functional entity to a communicationfacility or medium over it may communicate with other functionalentities or correspondent nodes.

The term “master base station” used in the claims and throughout thedescription of the present disclosure is to be construed as used in thefield of dual connectivity of 3GPP LTE-A; thus, other terms are macrobase station, or master/macro eNB; or serving base station or any otherterminology to be decided later by 3GPP. Similarly, the term “secondarybase station” used in the claims and throughout the description is to beconstrued as used in the field of dual connectivity of 3GPP LTE-A; thus,other terms are slave base station, or secondary/slave eNB or any otherterminology to be decided later by 3GPP.

The term “radio bearer” used in the claims and throughout thedescription of the present disclosure is to be construed in connectionwith 3GPP terminology, and refers to a virtual connection between twoendpoints, i.e. mobile station and base station, which is used fortransport of data between those; a term that emphasizes the fact thatthe virtual connection provides a “bearer service”, i.e. a transportservice with specific QoS attributes. A data radio bearer may also becalled user plane radio bearer, and a signaling radio bearer may also becalled control plane radio bearer. A radio bearer shall be distinguishedfrom other terminology as defined by 3GPP, such as S1 bearer, E-RAB,S5/S8 bearer, EPS bearer etc. (see also Figure 2.8 of LTE—The UMTS LongTerm Evolution FROM THEORY TO PRACTICE, Edited by: Stefania Sesia, IssamToufik, Matther Baker, Second Edition, ISBN 978-0-470-66025-6,incorporated herein by reference).

In the following, several embodiments of the present disclosure will beexplained in detail. For exemplary purposes only, most of theembodiments are outlined in relation to a radio access scheme accordingto 3GPP LTE (Release 8/9) and LTE-A (Release 10/11) mobile communicationsystems, partly discussed in the Technical Background section above. Itshould be noted that the present disclosure may be advantageously usedfor example in a mobile communication system such as 3GPP LTE-A (Release12) communication systems as described in the Technical Backgroundsection above. These embodiments are described as implementations foruse in connection with and/or for enhancement of functionality specifiedin 3GPP LTE and/or LTE-A. In this respect, the terminology of 3GPP LTEand/or LTE-A is employed throughout the description. Further, exemplaryconfigurations are explored to detail the full breadth of the presentdisclosure.

The explanations should not be understood as limiting the presentdisclosure, but as a mere example of the present disclosure'sembodiments to better understand the present disclosure. A skilledperson should be aware that the general principles of the presentdisclosure as laid out in the claims can be applied to differentscenarios and in ways that are not explicitly described herein.Correspondingly, the following scenarios assumed for explanatorypurposes of the various embodiments shall not limit the presentdisclosure as such.

According to the present disclosure, some of the drawbacks in some ofthe alternatives of series 3; e.g. 3C and 3D, shall be removed.Correspondingly, the present disclosure provides several embodimentswith regard to an improved buffer status reporting and logical channelprioritization procedure.

As explained before for the prior art, there is so far only one MACentity, even in carrier aggregation. So, it can only apply the LogicalChannel Prioritization, LCP, procedure once, even if it receives grantsfrom more than one cell/link. When the UE is requested to transmitmultiple MAC PDUs in one TTI, steps 1 to 3 and the associated rules ofthe standard LCP procedure may be applied either to each grantindependently or to the sum of the capacities of the grants. As a resultof the user plane architecture option 3, the UE will have 2 MAC entitiesthat receive separate grants from corresponding cell; but how the LCPwill be run (e.g. one by one or aggregately) is not clear, especiallyfor the shared bearer. Consequently, it is also not clear how the PBRallocation could work for such a bearer.

FIG. 15 schematically illustrates an S1-U interface terminating in MeNB,in addition to a radio bearer split in the MeNB, as well as independentRLCs for the split radio bearers. FIG. 17 schematically shows that inthe UP architecture options 3C and 3D, the PDCP is a common entity forthe RLC, MAC and PHY layers for the MeNB and SeNB.

In the following, the BSR will be considered first.

User plane architecture option Series 3 being considered in 3GPP, inparticular in 3GPP document TR 36.842, allows a bearer split such thatpackets from a particular bearer(s) can be received/transmitted via morethan one cell simultaneously from/to the UE.

In order to fulfil the QoS of all bearer(s) of each UE being served inthe network, different UL activities e.g. LCP, BSR, PHR and others canbe linked so that, once the UE knows e.g. how the BSR for the splitbearer has to be reported to each link/cell, it can also derive how thePBR derivation shall be done for running LCP for this split bearercorrespondingly in each MAC entity towards the individual participatingcell(s) or vice versa. This can be further linked to PHR such that aspecific PHR trigger may also trigger the BSR/PBR etc.re-derivation/re-computation and even reporting in that sense acorresponding new trigger.

An option is then to use a fixed ratio which can be semi-statically used(until re-derived/re-configured) to derive for example the BSR and theLCP parameters like the PBR. The ratio could be semi-statically fixed(hereafter called ‘fixed’) until changed later upon a freshderivation/signalling of the same.

An example thereof is illustrated in FIG. 18. As can be seen in thefigure, for a ratio of 1:4 split of Logical Channel 2 (LC2)—BSR in MeNBis reported for 110 and 99 Bytes for LCG1 and LCG2 respectively.Moreover, 133 and 78 Bytes are reported to SeNB for LCG1 and LCG2respectively.

More specifically, FIG. 18 schematically illustrates a UE side picture.Here, it is assumed that the BSR for only those channels are reportedinside an LCG that are actually received/transmitted between thecorresponding pair of MeNB-UE or SeNB-UE. As illustrated, in thisembodiment, there are two MAC entities in the UE, namely MAC-MeNB andMAC-SeNB, that calculate the buffer size corresponding to their part ofthe logical channels. In particular, in this example there are twoLogical Channel Groups, LCG1 and LCG2, where LCG1 has Logical ChannelsLC1 and LC4, while LCG2 has Logical Channels LC2 and LC3. As can beseen, only LC2 is the Split Bearer whose packets aretransmitted/received via both the MeNB and SeNB. Calculation of theBuffer Status Report adds the BO for all logical channels. BO for eachLogical Channel is RLC Buffer+PDCP Buffer. Further, the RLC BO (BufferOccupancy) is only reported to the corresponding Node, i.e. not shared,since RLC is per eNB. PDCP buffer is shared/split between thecorresponding MACs only if the related logical channel is split,otherwise not.

Therefore, for LC1, as an example, BSR to be reported to MeNB byMAC-MeNB is a simple sum of PDCP BO for LC1 (100 Bytes)+RLC BO for LC1(10 Bytes), and therefore, MAC-MeNB calculates the buffer sizecorresponding to the logical Channel LC1 as 110 Bytes. Since LCG1 forMAC-MeNB is only consisting of LC1 (LC4 also belonging to LCG1 refers toSeNB), the Buffer Status reported to MeNB (by MAC-MeNB) for LCG1 is 110Bytes.

Taking the example of Split Bearer case, LC2, since the example ratio is1:4, namely one part to the MeNB and four parts to the SeNB, the PDCP BOgets split in this ratio. That is, PDCP BO to be reported to MeNB byMAC-MeNB for LC2 is 80*1/5=16 Bytes. Since LC3 is also part of LCG2, thePDCP BO of LC3 is added directly, since LC3 is not a split-bearer.Therefore, PDCP Buffer Occupancy for LCG2 to be reported to MeNB byMAC-MeNB is 76, that is, 16+60 Bytes. Additionally, since the BufferStatus Report is the sum of PDCP BO+RLC BO, the corresponding BSR addsthe RLC BOs to this value. Therefore, MAC-MeNB calculates the buffersize corresponding to the logical Channels LCG2 as 99 Bytes, namely76+11+12 Bytes. Conversely, for reporting to the SeNB, the remainingpart of the PDCP BO for LC2 is used, namely 80*4/5=64 Bytes, to whichthe RLC BO is added, in this example, another 14 Bytes, resulting in atotal reported value to the SeNB of 78 Bytes.

In the above example 1:4 is only taken as an exemplary ratio; could berepresented also as 1/5:4/5 or 0.2:0.8. As another example, if the UEhas 100 Bytes of data to be sent in the UL for a particular split-bearerand the ratio derived and signalled by the network is 2:3 between theMeNB and SeNB for the same bearer, then the UE should report a bufferoccupancy of 40 Bytes to the MeNB and 60 Bytes to the SeNB. According toone advantageous implementation, this ratio is based primarily on howmuch traffic the network wants to offload to the Small Cell (e.g. 10%,50%, 99% or 100%).

If e.g. the ratio is 100%, then all the traffic shall be offloaded tothe Small Cell. Considering a corresponding ratio of 0:1, namely nothingto the MeNB and all to the SeNB, the PDCP BO gets split accordingly.When presuming the PDCP and RLC buffers of FIG. 18, this would result inthe following. For logical channel LC2, the PDCP BO to be reported tothe MeNB by MAC-MeNB is 0 bytes. As before, since logical channel LC3 isalso part of the group LCG2, the PDCP BO of 60 bytes for logical channelLC3 is added, and in this case completely due to not being a splitbearer. Therefore, PDCP BO for group LCG2 to be reported to the MeNB is60 bytes. To the 60 bytes for the PDCP BO, the corresponding RLC BOs forgroup LCG2 are to be added; this adds another 11 bytes and 12 bytes forlogical channels LC2 and LC3 respectively.

Conversely, for the BSR report to the SeNB, the full PDCP buffer for thesplit bearer is reported. In particular, the 80 bytes in the PDCP bufferfor LC2 are added completely to the RLC BO of 14 bytes for LC2. Thus,the complete BSR reports a total value 94 bytes (80+14).

This applies correspondingly to a special ratio of 0%, or 1:0, i.e. tothe case where no traffic shall be offloaded to the Small Cell. In thiscase, the full PDCP buffer for the split bearer LC2 is reported to theMeNB (in addition to the 60 bytes for LC3, and the RLC BO for LC2 andLC3), and nothing of the PDCP buffer for the split bearer LC2 isreported to the SeNB (although the RLC BO for LC2 is non-zero and stillreported to the SeNB).

The particular split ratios of 1:0 and 0:1 have the advantage of asimplified UE behaviour with respect to the BSR procedure for the splitbearer cases.

It is further advantageous, if buffer status reports are actually onlyreported when the value of the BSR is not zero. Put differently,especially in the above-mentioned cases where the PDCP BO may be 0 dueto the special split ratio of 1:0 or 0:1, the BSR basically reports theBO for the RLC layer, i.e. RLC BO reflecting the status of the receivedRLC PDUs in the downlink, to the SeNB. However, for those cases where nodata is in the buffer for the RLC layer (in this case for LC2), thecorresponding BSR that would be computed would have the value 0.Consequently, according to an advantageous embodiment, these kind of BSRwhich would report a value of 0 shall not be transmitted.

The fixed ratio can, for example, be derived by the network andsignalled to the UE. In some implementations, the MeNB is in charge ofdefining the ratio value, for instance by taking input such as the SeNBload factor from SeNB as well. In one embodiment, the eNB could signalthe ratio value to the UE using RRC Signalling (e.g. while(re)-Configuring a Bearer) or using MAC Signalling.

This ratio can tell the UE what fraction of the buffer needs to bereported to each of the participating cells for a particularsplit-bearer or, alternatively, to all the split-bearers, therefore itcan be implemented by using only one ratio per UE.

In some embodiments, the network nodes MeNB and SeNB can share thisallocated ratio information so that eNBs not only know how much UL grantwill be provided to the UE by the other eNB, for instance in the nextfew TTIs. This can give an indication of the resource/UL power usage ofthe other link, and then each link may provide its resource/UL powerusage accordingly.

For the particular ratios of 1:0 and 0:1 (i.e. no/full offloading tosmall cell), the network can signal how to split the total bufferoccupancy of the PDCP layer in different ways, as will be explained inthe following. For instance, the network may already indicate in thebearer configuration, which link should be used for the BSR reportingfor PDCP data as explained above. This may be done e.g. by a RadioResource Control (RRC) message e.g. by a radio resource configurationmessage. According to a first signalling implementation, a flag may beintroduced for a logical channel associated to a split EPS bearer. Theflag is thus indicating whether the UE should report PDCP data in thebuffer within a BSR for this logical channel or not. For instance, theflag may be included in the logicalChannelConfig information element,defined in the standard TS36.331, in a similar way as thelogicalChannelSR-Mask Information Element (IE). Alternatively, thedefinition of the “data becoming available” in the technical standardsTS 36.323, TS36.322 and TS 36.321 can be reused in said respect, suchthat the PDCP data shall only be considered for the BSR reporting andoptionally also for BSR triggering as “data becoming available” when theflag is set. This flag would basically indicate which of the two logicalchannels for a split bearer is used for BSR reporting of PDCP data. Oneof the two logical channels, either the one used for transmissionstowards the MeNB or the one towards the SeNB, would be enabled for BSRreporting of PDCP data, whereas the other one would be disabled (orsuspended) for BSR reporting of PDCP data.

According to a second signalling implementation, a new informationelement may be specified in either the MAC-MainConfig IE or DRB-ToAddModIE (already standardized in TS36.331), thus indicating whether the PDCPdata of a split bearer shall be considered by a specific radio bearer orlogical channel for BSR reporting or not.

Moreover, even if one of the links is configured to be disabled orsuspended for BSR reporting of PDCP data of a split bearer, this link isstill used for reporting RLC data of a split bearer, e.g. RLC STATUSPDUs, to the corresponding eNB. MAC Control elements (MAC CEs) like BSRor PHR which are also transmitted in the uplink are not radio bearerspecific data and hence are not in the scope of this present disclosure.

How the network, for instance the MeNB, derives the ratio could be basedon some specific criteria like cell load of participating cell,offloading requirements, such as how much traffic needs to be offloadedto SeNB, UE's UL channel conditions, such as which link is better/worse,QoS factors such as packet delay/bearer latency requirements, etc.

The BSR allocation may only apply to the buffer occupancy in the PDCPsub-layer, as in 3GPP document TS 36.323, but not e.g. to RLC sub-layerwhich may be reported “as-is” i.e. without any further splitting betweenthe MeNB and SeNB.

Further, the above ratio-based splitting may be subject to some “CertainMinimum Traffic/buffer” which may be configured to the UE or specified.For instance, the certain minimum range will be configurable i.e. whenthe network configures a bearer to the UE using an RRC ConnectionReconfiguration message; it may say that up to Index 20 of Table6.1.3.1-1: Buffer size levels for BSR (as described in 3GPP TS36.321-a40) is considered as below certain minimum range.

When the buffer occupancy of the combined PDCP and RLC is less that thisminimum threshold, then the UE may rather send its UL data to only oneof the link; the link itself could be based on UE's choice or could bepre-configured together with the minimum traffic/buffer occupancy. Asone possible alternative of this enhancement, the bearer type (e.g.signalling or specific data bearer like streaming, background etc.) maydetermine that the UE may only use a particular link for this datatransmission. The choice of link/bearer itself could bepre-configured/specified or based on UE's implementation choice.

According to a further embodiment, which may be used in addition oralternatively to the above and below described embodiments regarding theBSR splitting, any acknowledgements of the TCP layer associated with TCPdownlink data received in the UE are always to be transmitted to theMeNB. This is independent from whether the TCP ACKs refer to datareceived via the SeNB, and/or independent from whether or not otheruplink data is transmitted by the mobile node to the MeNB or SeNB.

TCP acknowledgements are transmitted in the uplink for each TCP downlinkdata packet received by the UE. Usually, TCP acknowledgements areprocessed as exemplified in FIG. 7, thus being encapsulated in the IPlayer and further by the PDCP layer as a PDCP PDU etc. In order to forceall TCP ACKs to be transmitted to the MeNB, the UE must detect these TCPACKs (or at least those TCP ACKs that would otherwise be transmitted tothe SeNB) and forward them over the appropriate logical channel to theMeNB (instead of to the SeNB). This may be achieved by the UE accordingto different implementations, some of which will be explained in thefollowing.

According to a first implementation, inter-layer notification(s) may bedefined between the TCP and the PDCP layers, thus allowing the PDCPlayer to identify the TCP ACKs and forward them to the appropriate RLCentity for further processing and transmission to the MeNB.

Alternatively, the PDCP layer may detect the TCP ACKs directly, i.e.without any inter-layer notification from the above layers, based e.g.on some implementation rules. For instance, usually TCP ACKs have afixed PDCP PDU size, and may thus be distinguished from other PDCP PDUs.Alternatively, the TCP/IP header identifies the data to relate to a TCPACK.

These detection procedures may be performed by the PDCP layer before IPheader compression.

In any case, the UE shall be able to direct all the TCP ACKs to theappropriate lower layers, for transmission to the MeNB.

As evidenced by simulation results, the TCP performance is directlyrelated to the RTT (Round Trip Time)/delay. Thus, the downlinkthroughput would be optimized/increased when the TCP ACKs do notexperience the additional X2 delay between the SeNB and the MeNB, andthe TCP RTT is reduced.

As mentioned before, this particular embodiment where all TCP ACKs areto transmitted to the MeNB, may be used in combination with any of theembodiments relating to the split ratio when calculating the BSR andwhen deactivating uplink transmission of PDCP data for a split bearer toone of the MeNB and SeNB. In these particular cases however, when thesplit bearer to the MeNB is deactivated (i.e. all traffic shall beoffloaded to the SeNB), the TCP ACKs shall not be offloaded but shall betransmitted to the MeNB (even though they are actually processed by thePDCP layer). This would allow the offloading of traffic to the SeNB,which is nearer to the UE, but would at the same time enhance the TCPperformance as explained above, by transmitting all TCP ACK to the MeNB.

For said reason, TCP uplink ACKs shall be treated as an exception to thedescribed procedure and must also be considered for the buffer statusreporting. As explained for the above embodiment, when the ratio is 0:1(i.e. all PDCP data is transmitted in the uplink to the SeNB, and theBSR is split by 0:1 with regard to the PDCP BO), the PDCP bufferoccupancy for TCP ACKs shall be indeed considered for the BSR reporting;as an exception to the above-mentioned embodiment. In particular, anyTCP ACKs occupying the PDCP buffer shall be reported to the MeNB in thecorresponding BSR, but shall not be reported to the SeNB; TCP ACKs shallbe thus treated differently from other data in the PDCP buffer, forwhich the split ratio shall indeed be applied. In other words, the splitratio, even when configured for the BSR reporting, shall not be appliedto TCP ACKs in the PDCP buffer.

Alternatively to the embodiment where the network determines the ratio,the fixed ratio could for example be derived by the UE itself, based ona variety of input parameters including one or more of the following butnot limited to:

-   -   Radio thresholds/HARQ re-transmissions (e.g. use a better radio        link more than a poor radio link)    -   History: Past grants received (higher grants received from a        particular cell would lead to higher ratio in its favour)

Generally, the UE's ratio derivation can be a function of theseparameters such that a more favourable cell, for example, which gavemore grants in the past time, such as 10/100/1000 ms, or which had asmaller HARQ operating point, receives a higher BSR/PBR ratio.

The ratio could be informed to the network by UL RRC or MAC signalling,enabling the network node(s) to know how much buffer occupancy is beingreported to the other node for the split-bearer.

In addition, for the non-split-bearer(s) that is received/transmittedbetween the UE and only one of the Network Nodes, i.e. so to say theSingle Connectivity bearer, the buffer occupancy of these could bereported to the ‘other node’. In other words, for instance, in FIG. 18,110 and 133 Bytes could be reported to the other nodes (SeNB and MeNBrespectively); this provides an indication to determine if the UE willhave high/low resource allocation (for example >1 Mbps) from the othernode. Accordingly, the MeNB/SeNB may schedule the UE to minimizeconflicts while allocating the radio resources including and affectingUE transmission power.

The buffer status is reported by a UE not per Logical Channel but for aLogical Channel Group. A Logical Channel Group may contain LogicalChannel(s) for Split Bearer(s) as well as Logical Channel(s) fornon-Split Bearer(s). The buffer status for Logical Channel(s) fornon-Split Bearer(s) may be reported to only the corresponding eNB (i.e.Buffer Status for a non-Split Bearer towards MeNB should be reported toonly MeNB; and similarly for SeNB). As a further enhancement, the bufferstatus for a non-Split Bearer towards MeNB may also be reported to SeNBand vice-versa. This will for example help the Master base station(MeNB) to determine how much scheduling the UE might receive in the nextfew subframes from the secondary base station, and accordingly themaster base station may schedule the UE to minimize conflicts whileallocating the radio resources. This could be for example helpful whileestimating the UE's total transmit power requirement in the next fewsubframes. This enhancement can be accomplished by configuring (by thenetwork towards the UE) and UE including in the Buffer Status Report 2parts, one each for MeNB and SeNB.

As for reporting BSR for Logical Channel(s) for Split Bearer(s): TheLogical Channel for Split Bearer(s) should be configured as a separateLogical Channel Group i.e. not including any Logical Channel(s) forNon-Split Bearer(s) in this group by the network. Mapping of bearers toa LCG should still be done in accordance to the priority of the bearers.Essentially only bearers of the same priority should be mapped into thesame LCG. Therefore, if split Bearers have a different priority theyshould presumable end up in separate LCGs.

So, buffer status for all the Logical Channel(s) for Split Bearer(s) canbe reported together in a LCG of its own. This may require the networkto configure more than 4 LCGs, as is (maximum 4 LCGs) currently thecase. In this case, network may internally decide (using Xn interface)to serve the UE in a specified ratio.

Or, alternatively, buffer status for the Logical Channel(s) for SplitBearer(s) may be computed for the UE as a whole (no segregation forMeNB/SeNB i.e. such that all PDCP BO is reported) and reported toeither/both of the eNB inside the corresponding LCG.

In the case when reporting the BSR (e.g. for split-bearer) to only oneof the Nodes, the UE could choose the node based on:

-   -   History, such as HARQ re-transmissions, Previous allocations        etc. to maximize the use of the link that is more suitable        according to the UE's UL channel condition and resource        availability in that Node.    -   The particular node could also be configured to be selected as        part of network policy that might dictate that under following        situations, the UE is supposed to choose a particular cell for        BSR reporting:    -   Radio Threshold, for instance, if DL RSRP, UL HARQ operating        point etc. are above a certain threshold then choose cell X for        BSR reporting,    -   buffer occupancy, for instance, if BO is less than a        predetermined value Threshold) then choose SeNB,    -   Choose the Cell to send the BSR where a D-SR, dedicated SR on        PUCCH. is configured,    -   Some UE implementation way.

As a possible enhancement, the UE can send the BSR to the othercell/link if the first cell/link did not provide much/any grant in aspecified amount of time such as, after the expiry of N retxBSR-Timer;where N is an integer greater than or equal to 1; for instance, if thefirst cell provided less than 50% of the grants that the UE asked for.

As yet another solution, the ratio values 0 (0:1), infinity (1:0) etc,could be used to switch off one of the links completely. For example, ifthe ratio 0 is signalled using the MAC signalling, then the UE will stopusing the first link (e.g. MeNB) completely (corresponding split beareror all the bearers depending on what the ratio denotes). Similarly, ifthe ratio infinity is signalled, then the UE will stop using the secondlink (e.g. SeNB).

In a more detailed implementation, the split ratios of 0:1 and 1:0,already considered for the BSR calculation as explained above, may inaddition or alternatively be used to deactivate the split bearer toeither the MeNB or the SeNB for transmitting data from the shared PDCPentity in the uplink. For instance, in line with the BSR reporting whenthe PDCP BO is fully reported to the MeNB for a split ratio of 1:0, thebearer to the SeNB may be deactivated or suspended and thus not used fortransmitting any uplink data, processed by the PDCP layer, to the SeNB.Conversely, in line with the BSR reporting when the PDCP BO is fullyreported to the SeNB for a split ratio of 0:1, the bearer to the MeNBmay be deactivated or suspended and thus not used for transmitting anyuplink data, processed by the PDCP layer, to the MeNB.

This has the advantage that the UE behaviour is simplified for the LCPprocedure for those split bearers, since bearer splitting thuseffectively only occurs in the downlink. Since all the uplink data(except RLC data) goes only to one eNB, the UE does not need todetermine how to split the PDCP buffer occupancy between the two eNBs.

FIG. 19, which is similar to FIG. 16, exemplarily illustrates thedeactivation of the bearer to cell 2 (the SeNB), in that the shared PDCPlayer (entity) forwards everything down to only the RLC layer entity forcell 1 (i.e. towards MeNB). FIG. 20 depicts the case where the bearertowards the MeNB is deactivated, and thus the shared PDCP layer (entity)forwards everything down to only the RLC layer entity for cell 2 (i.e.towards the SeNB).

As already mentioned above, even if one of the links is configured to bedisabled or suspended for uplink transmissions of PDCP data of a splitbearer, this link is still used for transmitting RLC data of the splitbearer, e.g. RLC STATUS PDUs, to the corresponding eNB. In other words,data that originates from the RLC entities may still be transmitted tothe corresponding base station, independent from the split ratio anddeactivation of a split bearer. Furthermore, MAC Control elements (MACCEs) like BSR or PHR which are also transmitted in the uplink are notradio bearer specific data and hence are not in the scope of thispresent disclosure; they are further transmitted to the correspondingbase station. As apparent from FIG. 19, data as generated by the lowerlayers of the PDCP (RLC, MAC) are still forwarded via Cell2 to the SeNB.

Optionally, A further exception relates to TCP acknowledgements, i.e.acknowledgments sent from the UE TCP layer in response to TCP downlinkdata received in the UE. As explained in a further embodiment, TCPAcknowledgements shall always be transmitted to one configured eNB, i.e.the MeNB, and thus in a split bearer case, TCP ACKs shall be forwardedfrom the PDCP layer to the corresponding lower layers so as to befurther forwarded to the MeNB; this shall be the case even for TCP ACKswhich relate to TCP downlink data received from the SeNB, and even forthe above case, where all PDCP data (which includes the TCP ACKsprocessed by the PDCP layer) is supposed to be transmitted to the SeNB.

This could e.g. lead to the scenario where all data is offloaded to theSeNB, with at least the exception of having all TCP uplink ACKs beingsent to the MeNB. According to another embodiment optionally, also PDCPstatus PDUs are sent always to one predefined eNB, e.g. MeNB in order toavoid the additional Xn delay. Similar to the TCP Acknowledgments, thePDCP entity would always forward a PDCP status report to thecorresponding lower layers so as to be further transmitted to the MeNBindependent from a split ratio or deactivation of an bearer. This coulde.g. lead to the scenario where all data is offloaded to the SeNB, withat least the exception of having all PDCP status PDUs being sent to theMeNB.

The UE may be informed about the split ratio, and thus about which linkof the split bearer to deactivate for the PDCP uplink data in variousways by the MeNB. As has been already explained in connection with thesplit ratio used in connection with the BSR calculation, the network mayalready indicate in the bearer configuration, whether the particularlink should be used for transmitting the PDCP uplink data or not; i.e.whether the particular link should be deactivated with respect totransmitting PDCP uplink data. This may be done by a Radio ResourceControl (RRC) message e.g. by a radio resource configuration message.

According to a first signalling implementation, a flag may be introducedfor a logical channel associated to a split EPS bearer. The flag is thusindicating whether the UE should use the particular logical channel fortransmitting the PDCP uplink data or not (and may additionally indicatewhether to report PDCP data in a BSR for this logical channel or not).For instance, the flag may be included in the LogicalChannelConfiginformation element, defined in the standard 36.331 in a similar way asthe logicalChannelSR-Mask Information Element (IE). Alternatively, thedefinition of the “data becoming available” in the technical standardsTS 36.323, TS36.322 and TS 36.321 can be reused in said respect.

According to a second signalling implementation, a new informationelement may be specified in either the MAC-MainConfig or DRB-ToAddMod(already standardized in TS36.331, thus indicating whether the UE shoulduse the particular radio bearer or respectively logical channel fortransmitting the PDCP uplink data or not (and may additionally indicatewhether to report PDCP data for transmission on this radio bearer orlogical channel or not).

The above-described BSR derivation ratio could also be used to run theLogical Channel Prioritization procedure e.g. by using the same, or aderived ratio to split the PBR (prioritisedBitRate). For example if aPBR of ‘kBps 128’ i.e. 128 Bytes per TTI is allocated in the ratio 1:3,i.e. for each Byte on MeNB, SeNB gets 3, then the effective PBR on thoselinks will be 32 and 96 respectively. With these derived PBRs, the LCPProcedure can be run in the 2 different MAC sub-layers, forcorresponding 2 different cells/links, as defined in the Logical ChannelPrioritization as defined in Section 5.4.3.1 of TS 36.321.

However, if no fixed ratio approach has to be used, then anotheralternative would be to use a Virtual Bucket Approach. In this approachMAC-1, corresponding to cell/link1, can run the LCP as usual and updatethe satisfied PBR situation (defined “Bj” as in Section 5.4.3.1 ofTS36.321, here incorporated by reference) of the split-beareraccordingly; the MAC-2, corresponding to cell/link2, can run the LCP asusual but taking for the split-bearer the new value (“Bj” as in Section5.4.3.1 of TS36.321) updated by the MAC-1 accordingly.

As to which MAC entity, for which link, should start to run the LCPprocedure first, there can be several mechanisms. This could be left toUE implementation; for instance some UE implementation may always startwith the SeNB, and others may always start with the MeNB; alternatively,other UE implementation may decide randomly, or based on the grant thatwas received earlier for one of the links.

In one possible example, if most for instance more than 50% of the grantwas provided by a particular eNB, then the UE can start with this eNB'sgrant. As a further option the UE could toggle the first MAC (cell/link)based on a similar criteria or could even be configured by the network,for instance by starting with the cell (BO occupancy corresponding tothis cell) which has less unhappiness in terms of less aggregated datato be transmitted etc. The Unhappiness can be calculated by aggregatingthe unsatisfied PBR and/or the remaining amount of the data in thebuffer. Further, in the MAC entity selected this way, the highestpriority Bearer's unhappiness can be minimized first by allocating theextra grants to it and then going on to the lower priority unhappybearers sequentially.

As an alternative solution to when no fixed ratio approach has to beused, the network could configure the division in time, such as in TDMfashion, of when which MAC will run the LCP considering the splitbearer(s). The other MAC does not consider this split bearer(s) forthese time slots but otherwise run the LCP normally for all otherbearer(s).

As a further alternative solution to when no fixed ratio approach has tobe used, more Steps could be added to the procedure described in Section5.4.3.1 of 3GPP TS36.321 such that first CP is run normally in both theMAC entities and then one of the MAC that has highest unhappiness triesto reduce the unhappiness by taking off the allocations to the splitbearer such that a Negative Bj, if any, of the split bearer just getsback to 0. These grants are then distributed to other bearer(s) if theirBj was still positive, else (or if the grant was still remaining)allocating the grant to other high priority bearers, starting with thehighest priority bearer that has still any data in its buffer such thatthe highest priority Bearer's unhappiness can be minimized first byallocating the extra grants to it and then going on to the lowerpriority unhappy bearers sequentially.

In the following, further alternative approaches will be disclosed.

As a yet another alternative solution to when no fixed ratio approachhas to be used, the grants from all the cell/link could be aggregated asone grant, and then the LCP procedure could be run such that the sum ofthe so far allocated grant to the logical channels in a cell does notexceed the grant that was coming from that cell, and, when this happens,the LCP procedure shall allocate grant to the remaining Logical Channelof the other MAC-cell.

As yet another alternative for Logical Channel Prioritization, thenetwork (RRC) could configure the split-bearer as two separateconfigurations, corresponding to two different cells, in the UE suchthat the PBR (prioritisedBitRate) or other parameters that RRC controlsfor the scheduling of uplink data by signalling for each logical channelhas different values for each PBR (prioritisedBitRate) or otherparameters that RRC controls for the scheduling of uplink data.

Thereafter, each MAC entity in the UE may run its LCP independently.What values of such parameter could be configured might be a decisionsimilar to “ratio” derivation that was described above. As animplementation option the UE could also configure itself in this similarmanner, that is, configure internally the split-bearer as two separateconfigurations.

Further, putting the different UL Scheduling procedures together can bedone such that these not only share, for example, the ratio but also thetrigger. This could for example happen when one of the cell goes down(like meets RLF or cannot be used for a similar reason), then the UEshould report the BSR, PHR assuming no transmission for the bad link andchange the ratio (that is used to work out the BSR, LCP and even PHR)such that it is clear to the receiving network node that the other linkis down and/or that it needs to/can provide a higher grant (power,physical resources) to the UE and also initiate a subsequent necessaryprocedure including the mobility of the UE to some other cell using e.g.the Handover Procedure. In this cell a change of one situation likePower (PHR report) may subsequently trigger the other reports like BSR,and also the UL logical channel prioritization should also account forthese changes such that a split-bearer does not suffer/suffers minimallyin the transmission. So, whenever RLF happens, the UE could signal usingspecial reporting (implicitly or explicitly) in one of thesereports/procedure that RLF has happened, and then the network couldinitiate some kind of recovery mechanism.

In the following a further embodiment of the present disclosure will bedescribed according to which the Logical Channel Prioritizationprocedure considers the split bearer, and particularly the split bufferstatus reporting as introduced in any of the previous embodiments.

According to one of the previous embodiments, the PDCP buffer for thesplit bearer (e.g. LC2 in FIG. 18) is shared between the radio bearer tothe MeNB and the radio bearer to the SeNB. This may lead to a waste ofuplink grant during the LCP procedure as will be exemplified by thefollowing scenario.

The UE is assumed to be configured with an eNB-specific bearer RB1,mapped only to the MeNB, and with a “split bearer” RB2, mapped both tothe MeNB and the SeNB. Additionally, BSR reporting for the split bearerRB2 shall be configured with a ratio of 0.4 to 0.6. Assuming that 100bytes of (PDCP) data arrive for both bearer simultaneously, the UE wouldcorrespondingly send a first BSR1 with 140 bytes (100 bytes+0.4*100bytes) to the MeNB, and a second BSR2 with 60 bytes (0.6*100 bytes) tothe SeNB.

First, the UE is scheduled with a grant of 140 bytes from the MeNB.Provided the Logical Channel priority of RB2 is higher than priority ofRB 1 and when performing the common LCP procedure for a split bearer asdescribed in the embodiment above, the UE sends 100 bytes of data viaRB2 towards MeNB, and 40 bytes of data via RB1 towards MeNB. Later, theUE receives another grant of 60 bytes from the SeNB. However, there isno data left for any bearers mapped towards the SeNB, and the UE may notuse the grant from the SeNB for data towards the MeNB. Thus, the UEsends padding bytes to the SeNB, and the data of RB1 pending for uplinktransmission towards MeNB waits in the UE buffer, until the MeNBreceives new information on the buffer status, e.g. via a periodic BSR.As apparent, the present LCP procedure is inefficient when implementingthe embodiments where the PDCP buffer occupancy is split and only asplit PDCP BO is reported to the eNBs.

According to this further embodiment, the LCP procedure is adapted toconsider that only part of the PDCP BO is reported to the two eNBs. Inparticular, at least the first and third steps of the LCP procedurewould be specified in a similar manner as follows:

Step 1: All the logical channels with Bj>0 are allocated resources in adecreasing priority order. If the PBR of a radio bearer is set to“infinity”, the UE shall allocated resources for all the data that isavailable for transmissions on the radio bearer before meeting the PBRof the lower priority radio bearer(s), but only up to a maximum of thebuffer occupancy reported to the base station;

Step 2: if any resources remain, all the logical channels are served ina strict decreasing priority order (regardless of the value of Bj) untileither the reported data for that logical channel or the UL grant isexhausted, whichever comes first. Logical channels with equal priorityshould be served equally.

Therefore, when performing the two LPC procedures (one for eachdirection of the split bearer, towards the MeNB and SeNB), in the abovementioned scenario a waste of resources is avoided. In this example,When receiving the first grant of 140 bytes from the MeNB, instead ofserving resources for sending all 100 bytes of data of the RB2 to MeNB,only 40 bytes are transmitted by the UE via RB2 to the MeNB, since only40 bytes were reported with the BSR1 regarding the RB2. Out of theremaining 100 bytes of this first grant from the MeNB, 100 bytes arespent to transmit the 100 bytes of data waiting for RB1 towards theMeNB. Then, when receiving to the second grant of 60 bytes from theSeNB, the remaining 60 bytes waiting for RB2 are transmitted using acorresponding amount of resources from this second grant.

For the case that one radio bearer or logical channel of a split beareris deactivated or suspended for UL transmission of PDCP data, the LCPprocedure will only consider data in the RLC entity of thisdisabled/suspended logical channel but no data available in the PDCPentity for this disabled/suspended logical channel.

According to another further embodiment, the LCP procedure for splitbearers considers a virtual PDCP buffer for each of the link/bearers thesplit bearer is using in the uplink Since the PDCP entity is sharedbetween the two RLC/MAC entities in the case of a split bearer as shownin FIG. 16, the UE is creating a virtual PDCP buffer/entity for each ofthe cells which are used in LCP procedure in the two MAC entities. ThePDCP buffer occupancy of a virtual PDCP entity/buffer is calculated bythe PDCP buffer occupancy of the shared PDCP entity multiplied with theconfigured split ratio. For example, in case the PDCP buffer occupancyof the shared PDCP entity is 100 bytes at one time instance and theconfigured split ratio is 0.4 to 0.6, then BO of the virtual PDCPbuffer/entity for cell 1 (towards MeNB) is 40 bytes whereas the BO ofthe virtual PDCP buffer/entity of cell (towards SeNB) is 60 bytes. Theadvantage of the virtual PDCP buffer/entities is that the normal LCPoperations can be done for a split bearer as described in aboveembodiment.

In the following, a further embodiment of the present disclosure will beexplained. It is assumed that a split bearer is present, i.e. an EPSbearer is split across MeNB and SeNB. However, it is yet unspecified howthe triggering of the BSR by the MAC entities will be handled by the UE.When data arrives in the buffers of the split bearer and a BSR istriggered in MAC entity (be it MAC-MeNB or MAC-SeNB), the other MACentity (MAC-SeNB or MAC-MeNB) might not be triggered.

According to a first option, the BSR trigger in one of the MAC entitiesfor the split bearer is indeed not propagated to the other MAC entity.Rather, the one MAC entity shall report the BSR to its correspondingbase station, while the other MAC entity shall report the BSR whentriggered itself (e.g. by arrival of data, or by a periodic BSRtrigger). The corresponding split-ratios can be considered for therespective calculation of the two BSR. In this case, the reporting bythe two MAC entities of the split bearer is completely independent,which facilitates implementation.

According to a second option, the BSR trigger in one of the MAC entities(be it MAC-MeNB or MAC-SeNB) is propagated to the other MAC entity, suchthat this other MAC entity will also internally trigger the BSR;effectively, the MAC entities of the split bearer will always betriggered together to report the BSR and thus two buffer status reportsare to be transmitted, one to the MeNB and one to the SeNB. However,depending on how the uplink resources for the BSR reporting arescheduled, the two transmissions of BSR are likely to happen atdifferent times in the two cells. Therefore, the buffer occupancy of thesplit bearer might have changed, i.e. new data could arrive in thebuffer between the two transmission time instances, which leads toproblems on how to handle such situations, especially with regard to thelater BSR report.

This embodiment thus also deals with the question of how the two BSR areto be calculated with respect to each other, and different options arepossible, four of which will be explained in greater detail. TO shall bethe time at which the two MAC entities are triggered for BSR reporting;T1 shall be the time at which the first BSR is scheduled to betransmitted (be it the BSR-MeNB, or the BSR-SeNB); correspondingly, T2shall be the time at which the second BSR is scheduled to be transmitted(be it the BSR-SeNB or the BSR-MeNB).

According to a first calculation option, both of the BSR are calculatedbased on the buffer occupancy at either T0 (i.e. when the BSR aretriggered) or at T1 (i.e. when the first one is to be transmitted). Thesplit-ratio can be respectively applied for the calculation of the twoBSRs. UE needs to store the PDCP buffer occupancy at T0 or T1 in orderto perform the calculation of BSR at T2.

According to a second calculation option, the first-timed BSR iscalculated with the buffer occupancy at either T0 or T1, and thentransmitted as scheduled at T1. Then, the second-timed BSR is calculatedto be the buffer occupancy at time T2, minus what was already reportedby the first-time BSR; i.e. equal to BO_T2−reported BO_T1/0. Thus,although at time T0 or T1, the split ratio can be applied to thisfirstly-timed BSR, for the secondly-timed BSR the split-ratio shall notbe applied, since the value of this secondly-timed BSR reflects thedifference of the BO at T2 vis-a-vis the reported BO at time T1 or T0.The advantage of this second calculation option is that the entirebuffer occupancy is reported to eNBs.

According to a third calculation option, the two BSRs are calculatedindependently from each other at basically the corresponding times whenthey are transmitted. Thus, the firstly-timed BSR is calculated based onthe BO at time T1, while the secondly-timed BSR is calculated based onthe BO at time T2. Again, in both cases the split-ratio may be appliedrespectively, as explained in one of the various embodiments discussedbefore. This option has the advantage that the BSR reporting procedurecan be performed independently in the two MAC entities which ispreferable from implementation point of view.

According to a fourth calculation option, the firstly-timed BSR (e.g.for the MeNB) is calculated at time T1 based on the BO at time T1 (withuse of the corresponding split ratio). Furthermore, at time T1 also thevalue for the other BSR (e.g. for the SeNB) is calculated based on theBO at time T1 (with use of the corresponding split ratio); however, thisone is not transmitted but merely stored for later use. In particular,at time T2 the UE shall calculate a BSR based on the newly-arrived data(i.e. data arrived between T1 and T2) (also applying the split ratioaccordingly), and add this to the stored value of the BSR (e.g. for theSeNB) as calculated at time T1. The thus resulting value is thenreported at T2, as scheduled.

The differences of these four options will be illustrated according tothe following exemplary scenario. It is assumed, that the buffer statusat TO and T1 is 100 bytes. New data of 200 bytes is supposed to arrivebetween T1 and T2. A split ratio of 0.3 to 0.7 for MeNB to SeNB isdefined. At time T1 the BSR for the MeNB is scheduled; at time T2 theBSR for the SeNB is scheduled.

TABLE 2 BO reported at T1 BO reported at T2 Option 1 30 (0.3*100)  70(0.7*100) Option 2 30 (0.3*100) 270 (300 − 30) Option 3 30 (0.3*100) 210(0.7*300) Option 4 30 (0.3*100) 210 ((0.7*200) + 70)

This present disclosure further looks into the aspect of transportingthe Signalling Radio Bearer (RRC Signalling messages) between the MeNBand UE RRC using the Layer 2 scheduling/Transport of UE-SeNB link.

In Normal circumstances for Signalling Radio Bearer (RRC Signallingmessages) Layer 2 transport only RRC->PDCP->RLC-M->MAC-M might besufficient; but we need to have the other possibility ofRRC->PDCP->RLC-S->MAC-S for the same SRB at some special conditions likewhen the MeNB would want to have RRC Diversity (i.e. sent the RRCmessage via both MeNB and SeNB links so as to ensure that the UEreceives the RRC Signalling message through at least one link) or whenthe Radio Link has failed towards one of the eNBs and the UE may want tosend a reporting message to report the situation (includingMeasurements) to the RRC in MeNB (via the available MeNB or SeNB link)

Layer 2 transports of SRBs, in the DL, from the UE's perspective wouldmean that the UE needs to be configured for receiving some SRBs fromSeNB as well. Since MAC-S will anyway be available (corresponding toSeNB), the only further configuration required would be likely forRLC-S. If the RLC-S configuration would be exactly the same as RLC-M,then UE implementation can ensure that SRB packets are delivered to RRCby both MAC-M and MAC-S similarly e.g. by having a SAP (Service AccessPoint) between the MAC-S and RLC-M; this enhanced implementation aspectworks such that this SAP is always available or alternatively, thenetwork should activate this SAP (or configure/activate RLC-S) when itintends to send a DL RRC message via the SeNB L2 transport. UEimplementation “can” ensure that SRB packets are delivered to RRC by L2of MAC-M and MAC-S entities by having always a dedicated SAP betweenthem. However, in one further alternative network may specificallycontrol when the SRB from the SeNB L2 will be delivered by way of MAC orRRC level signalling (thereby sort of activating this link between theMAC-M and MAC-S entities).

In the UL however, since in normal circumstances, the RRC packets shouldnot be unnecessarily duplicated and sent across 2 different links butonly upon special conditions (using same/different RRC transactionidentifiers) whereby RRC/PDCP can trigger/activate this in the lowerlayer and later come back to 1 link SRB transmission. This can be doneby UE RRC when it needs to:

-   -   respond to a RRC Signalling message that was received on SeNB L2        link    -   initiate a RRC Signalling message on SeNB L2 link when MeNB L2        link is not available due to Radio Link failure    -   initiate a RRC Signalling message on MeNB L2 link when SeNB L2        link is not available due to Radio Link failure    -   a critical information needs to be sent in the Uplink

For the above enhancements related to SRB delivery via the L2 SeNB link,the network may need to configure relevant parameters in UE RRC andlower layers and enable MAC signalling when required. This networkconfiguration may allow the duplication of RRC messages on the L2 SeNBlink, use of MAC/RRC signalling for this purpose and even configure thescenarios where this new UE behaviour would be required.

Hardware and Software Implementation of the Present Disclosure

Another embodiment of the present disclosure relates to theimplementation of the above described various embodiments using hardwareand software. In this connection the present disclosure provides a userequipment (mobile terminal) and eNodeBs (master and secondary basestation). The user equipment is adapted to perform the methods describedherein.

It is further recognized that the various embodiments of the presentdisclosure may be implemented or performed using computing devices(processors). A computing device or processor may for example be generalpurpose processors, digital signal processors (DSP), applicationspecific integrated circuits (ASIC), field programmable gate arrays(FPGA) or other programmable logic devices, etc. The various embodimentsof the present disclosure may also be performed or embodied by acombination of these devices.

Further, the various embodiments of the present disclosure may also beimplemented by means of software modules, which are executed by aprocessor or directly in hardware. Also a combination of softwaremodules and a hardware implementation may be possible. The softwaremodules may be stored on any kind of computer readable storage media,for example RAM, EPROM, EEPROM, flash memory, registers, hard disks,CD-ROM, DVD, etc.

It should be further noted that the individual features of the differentembodiments of the present disclosure may individually or in arbitrarycombination be subject matter to another present disclosure.

It would be appreciated by a person skilled in the art that numerousvariations and/or modifications may be made to the present disclosure asshown in the specific embodiments without departing from the spirit orscope of the present disclosure as broadly described. The presentembodiments are, therefore, to be considered in all respects to beillustrative and not restrictive.

1. A communication method for a mobile node connectable to a master basestation and to a secondary base station by using a split bearer splitacross the master base station and the secondary base station, wherein aPacket Data Convergence Protocol, PDCP, layer located in the mobile nodeis shared for the split bearer between the master base station and thesecondary base station, the method comprising: splitting by the mobilenode a total buffer occupancy of the PDCP layer in the mobile nodebetween the master base station and the secondary base station based ona split ratio, into a first PDCP buffer occupancy value for the masterbase station and a second PDCP buffer occupancy value for the secondarybase station; generating by the mobile node a first buffer status reportfor the master base station based on the first PDCP buffer occupancyvalue, and generating a second buffer status report for the secondarybase station based on the second PDCP buffer occupancy value; andtransmitting by the mobile node the first buffer status report to themaster base station, and transmitting the second buffer status report tothe secondary base station.
 2. The communication method according toclaim 1, wherein a particular split ratio is defined such that one ofthe first and second PDCP buffer occupancy values is equal to the totalbuffer occupancy of the PDCP layer in the mobile node for the splitbearer, and such that the other one of the first and second PDCP bufferoccupancy values is equal to zero, preferably wherein said particularsplit ratio is 1 to 0 or 0 to
 1. 3. The communication method accordingto claim 1, wherein, when being configured with the particular splitratio, the mobile node transmit all uplink data, processed by the PDCPlayer, to either the master base station or the secondary base stationdepending on the particular split ratio, with the exception of RLCuplink data being transmitted to the respective base station.
 4. Thecommunication method according to claim 1, wherein, when beingconfigured with the particular split ratio, the mobile node deactivatesthe split bearer for uplink data, processed by the PDCP layer, to eitherthe master base station or the secondary base station depending on theparticular split ratio.
 5. The communication method according to claim1, wherein the mobile node is informed by the master base station abouthow to split the total buffer occupancy of the PDCP layer in the mobilenode between the master base station and the secondary base station,preferably by a flag in an information element associated with the splitbearer.
 6. The communication method according to claim 1, wherein afirst Radio Link Control, RLC layer is located in the mobile node forthe split bearer to the master base station, and a second RLC layer islocated in the mobile node for the split bearer to the secondary basestation; the first buffer status report is generated by the mobile nodebased on the sum of the first PDCP buffer occupancy value and a bufferoccupancy value of the first RLC layer in the mobile node; and thesecond buffer status report is generated by the mobile node based on thesum of the second PDCP buffer occupancy value and a buffer occupancyvalue of the second RLC layer in the mobile node.
 7. The communicationmethod according to claim 6, wherein a particular split ratio is definedsuch that one of the first and second PDCP buffer occupancy values isequal to the total buffer occupancy of the PDCP layer in the mobile nodefor the split bearer, and such that the other one of the first andsecond PDCP buffer occupancy values is equal to zero, and wherein incase the first/second buffer status report is zero, the first/secondbuffer status report is not transmitted.
 8. The communication methodaccording to claim 1, wherein the mobile node is configured to transmitall the acknowledgements of the Transmission Control Protocol, TCP,layer, relating to TCP downlink data received in the mobile node, to themaster base station, preferably independent from whether or not theremaining uplink data is transmitted by the mobile node to the masterbase station.
 9. The communication method according to claim 8, whereinthe PDCP layer of the mobile node detects TCP acknowledgments andinternally forwards the detected TCP acknowledgements to lower layers tobe transmitted via a channel to the master base station.
 10. Thecommunication method according to claim 8, wherein the calculation ofthe first buffer status report considers the transmission of all theacknowledgements of the TCP layer to the master base station,irrespective of the split ratio.
 11. The communication method accordingto claim 1, further comprising: performing by the mobile node a firstLogical Channel Prioritization, LCP, procedure for the split bearer tothe master base station, based on the value of the buffer occupancy forthe split bearer to the master base station reported with the firstbuffer status report; and performing by the mobile node a second LogicalChannel Prioritization, LCP, procedure for the split bearer to thesecondary base station, based on the value of the buffer occupancy forthe split bearer to the secondary base station reported with the secondbuffer status report.
 12. The communication method according to claim11, wherein the value of the buffer occupancy reported with the firstbuffer status report is considered in the first LCP procedure by servingresources to the split bearer to the master base station as a maximum upto the value of the buffer occupancy reported with the first bufferstatus report for the split bearer to the master base station, andwherein the value of the buffer occupancy reported with the secondbuffer status report is considered in the second LCP procedure byserving resources to the split bearer to the secondary base station as amaximum up to the value of the buffer occupancy reported with the secondbuffer status report for the split bearer to the secondary base station.13. The communication method according to claim 1, wherein a first MediaAccess Control, MAC, layer is located in the mobile node for the splitbearer to the master base station, and a second MAC layer is located inthe mobile node for the split bearer to the secondary base station, themethod further comprising: when buffer status reporting is triggered inthe first MAC layer due to data arrival in the buffer of the splitbearer triggering by the first MAC layer the buffer status reporting inthe second MAC layer for the split bearer; and when buffer statusreporting is triggered in the second MAC layer due to data arrival inthe buffer of the split bearer triggering by the second MAC layer thebuffer status reporting in the first MAC layer for the split bearer. 14.The communication method according to claim 13, wherein the first bufferstatus report is generated by the first MAC layer at the time of beingtriggered, and the second buffer status report is generated by thesecond MAC layer at the time of being triggered, or wherein in case thefirst buffer status report is scheduled to be transmitted before secondbuffer status report, the first buffer status report is generated by thefirst MAC layer at the time the first buffer status report is scheduledto be transmitted to the master base station, and the second bufferstatus report is generated by the second MAC layer at the time the firstbuffer status report is scheduled to be transmitted to the master basestation, and or the first buffer status report is generated by the firstMAC layer at the time the first buffer status report is scheduled to betransmitted to the master base station, and the second buffer statusreport is generated by the second MAC layer at the time the secondbuffer status report is scheduled to be transmitted to the secondarybase station, or the first buffer status report is generated by thefirst MAC layer at the time the first buffer status report is scheduledto be transmitted to the master base station or at the time the firstbuffer status report is triggered at the first MAC layer, and the secondbuffer status report is generated by the second MAC layer at the timethe second buffer status report is scheduled to be transmitted to thesecondary base station, wherein the second buffer status report includesthe value of the data not reported by the first buffer status report.15. A mobile node connectable to a master base station and to asecondary base station by using a split bearer split across the masterbase station and the secondary base station, wherein a Packet DataConvergence Protocol, PDCP, layer located in the mobile node is sharedfor the split bearer between the master base station and the secondarybase station, the mobile node comprising: a processor adapted to split atotal buffer occupancy of the PDCP layer in the mobile node between themaster base station and the secondary base station, based on a splitratio, into a first PDCP buffer occupancy value for the master basestation and a second PDCP buffer occupancy value for the secondary basestation; a processor adapted to generate a first buffer status reportfor the master base station based on the first PDCP buffer occupancyvalue, and to generate a second buffer status report for the secondarybase station based on the second PDCP buffer occupancy value; and atransmitter adapted to transmit the first buffer status report to themaster base station, and transmitting the second buffer status report tothe secondary base station.